From: James Smart <James.Smart@Emulex.Com>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: Daniel Debonzi <debonzi@linux.vnet.ibm.com>,
"scst-devel@lists.sourceforge.net"
<scst-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [Scst-devel] Discussion about SCST sysfs layout and implementation.
Date: Fri, 17 Apr 2009 10:27:20 -0400 [thread overview]
Message-ID: <49E891C8.1050007@emulex.com> (raw)
In-Reply-To: <49E88E3F.8030107@vlnb.net>
Vladislav Bolkhovitin wrote:
> Let's go with root in /sys/class/scsi_tgt. In future, if somebody
> objects, we can easily change it.
>
This maps too closely to the scsi midlayer names, especially the real
target devices initiators see - which are not yet in sysfs but there has
been discussion of in the past. I would prefer that you used
/sys/class/scst_tgt. And yes, as part of the class level support in the
midlayer/kernel, they are generally symlinks to the actual kobject in
the /sys/devices that the class entity corresponds to.
IMHO - "scsi_tgt" also seems a bit presumptuous to propose if SCST is
not, in it's entirety, going to be the adapter target interface pulled
in upstream. Thus, another reason I prefer the "scst_tgt" name, as it
makes it very specific to SCST itself, and lessens any co-existence
conflicts if there are any in the future.
-- james s
next prev parent reply other threads:[~2009-04-17 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 13:19 [RFC]: SCST sysfs layout Vladislav Bolkhovitin
[not found] ` <49E77795.7080204@linux.vnet.ibm.com>
2009-04-17 10:51 ` [Scst-devel] Discussion about SCST sysfs layout and implementation Vladislav Bolkhovitin
2009-04-17 13:25 ` Daniel Debonzi
2009-04-17 14:12 ` Vladislav Bolkhovitin
2009-04-17 14:27 ` James Smart [this message]
2009-04-17 17:43 ` Vladislav Bolkhovitin
2009-04-17 17:56 ` Kay Sievers
2009-04-17 18:24 ` Kay Sievers
2009-04-23 16:11 ` Daniel Debonzi
2009-04-28 17:02 ` Vladislav Bolkhovitin
2009-04-17 14:24 ` Kay Sievers
2009-04-17 15:50 ` Daniel Debonzi
2009-04-17 16:03 ` Kay Sievers
2009-04-17 17:42 ` Vladislav Bolkhovitin
2009-04-17 17:43 ` Vladislav Bolkhovitin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E891C8.1050007@emulex.com \
--to=james.smart@emulex.com \
--cc=debonzi@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=scst-devel@lists.sourceforge.net \
--cc=vst@vlnb.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).