Re: targetcli and user-backed backstores, advice?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 05/11/2015 11:40 PM, Andy Grover wrote:
On 05/11/2015 02:05 PM, Jerome Martin wrote:


On 04/22/2015 10:01 PM, Andy Grover wrote:
On 04/22/2015 12:46 AM, Christophe Vu-Brugier wrote:
What about removing backstores/user and prefixing the user-backed
backstores names:

+-- backstores
     |-- block
     |-- fileio
     |-- pscsi
     |-- ramdisk
     |-- user:file
     +-- user:glfs

Sure, we could do this. It lets the user clearly know e.g. glfs is
userspace-backed, but still suggests the user can configure it the same
way as the built-in backstores.

What about using something that makes it explicit, like:

|-- file (externally managed)

or something to that effect?

We could put that in the summary (over on the right) but the actual node
names are paths that people can "cd" into, so we probably want to limit
what we put there, no?

Oh yes, obviously. Sorry, the formatting within the email reply was not up to the task, but this is what I meant.

As for the names themselves, I think Christophe suggestion of using a prefix makes sense to prevent possible name clashes with the regular backstores, unless you can guarantee that this cannot happen?
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux