From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Daniel Debonzi <debonzi@linux.vnet.ibm.com>
Cc: scst-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [Scst-devel] Discussion about SCST sysfs layout and implementation.
Date: Fri, 17 Apr 2009 18:12:15 +0400 [thread overview]
Message-ID: <49E88E3F.8030107@vlnb.net> (raw)
In-Reply-To: <49E8832F.6070302@linux.vnet.ibm.com>
Daniel Debonzi, on 04/17/2009 05:25 PM wrote:
>>> Vladislav Bolkhovitin wrote:
>>>> Hi All,
>>>>
>>>> Below is proposal for the SCST sysfs layout, which will replace
>>>> existing procfs-based infrastructure. Any comments, questions and
>>>> suggestions are welcome!
>>>>
>>>> I. SCST sysfs layout.
>>>>
>>>> Root would be /sys/scsi_tgt.
>>>>
>>>> In the root there would be the following files and subdirectories:
>>>>
>>>> - targets - subdirectory listing names of all registered target
>>>> drivers.
>>>>
>>>> - devices - subdirectory listing all registered backend devices.
>>>>
>>>> - sgv - subdirectory listing all existing SGV pools.
>>>>
>>>> - drivers - subdirectory listing all loaded target and backend
>>>> drivers (dev handlers).
>>>>
>>>> - threads - RW file listing number of global SCST threads. Writing
>>>> to that file would allow to change that value.
>>>>
>>>> - trace_level - RW file listing SCST core logging level. Writing to
>>>> that file would allow to change that. Example content: "out_of_mem |
>>>> minor | pid | line | function | special | mgmt | mgmt_minor |
>>>> mgmt_dbg | retry". See current procfs implementation of this file for
>>>> more info.
>>>>
>>>> - version - RO file listing version of SCST core and enabled compile
>>>> time features. Example content: "1.0.2, EXTRACHECKS,
>>>> DEBUG"
>>>
>>> Based on all I read this last days, I believe we are not allowed to
>>> include the directory scsi_tgt on /sys root. I think it has to be in a
>>> existent directory reserved for this sort of application. I just
>>> didn't figured out which one it would be.
>> /sys/class? It already has scsi_device, scsi_disk, scsi_generic and
>> scsi_host.
>
> I don't think so because all the directories on /sys/class have symlinks
> to the files somewhere else. However I noticed that many of them on my
> system are on /sys/device/virtual
Let's go with root in /sys/class/scsi_tgt. In future, if somebody
objects, we can easily change it.
Vlad
next prev parent reply other threads:[~2009-04-17 14:12 UTC|newest]
Thread overview: 19+ 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 [this message]
2009-04-17 14:27 ` James Smart
2009-04-17 17:43 ` Vladislav Bolkhovitin
2009-04-17 17:56 ` Kay Sievers
2009-04-17 17:56 ` Kay Sievers
2009-04-17 18:24 ` 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 14:24 ` Kay Sievers
2009-04-17 15:50 ` Daniel Debonzi
2009-04-17 16:03 ` Kay Sievers
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=49E88E3F.8030107@vlnb.net \
--to=vst@vlnb.net \
--cc=debonzi@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=scst-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.