From: James Bottomley <James.Bottomley@steeleye.com>
To: "Surekha.PC" <surekhap@cisco.com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
'Naveen Burmi' <naveenb@cisco.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
davmyers@cisco.com
Subject: RE: Request for review of Linux iSCSI driver version 4.0.0.2
Date: 01 Dec 2003 09:40:08 -0600 [thread overview]
Message-ID: <1070293210.1778.25.camel@mulgrave> (raw)
In-Reply-To: <002b01c3b7f8$5e6fbf20$a0074d0a@apac.cisco.com>
On Mon, 2003-12-01 at 04:46, Surekha.PC wrote:
> Our driver has lot of user space attributes. Making each attribute as a
> separate file will endup with lots of files. So we want to have all
> target specific attributes together in one file and lun specific
> attributes in another file for convinience. find_keyword() will help
> search for these keys from the cmdline specified.
>
> Pls let me know your suggestions.
I count 35 total (for both host and target); that's well within the
range of the sysfs single file per value. A lot of them also seem to be
debug attributes, so won't they go away (or at least only compile in
under a DEBUG #define) with the released product?
The idea behind sysfs is easily and uniformly to export data to the
user, and to import it from the user. You could separate the properties
out into those which are useful to the end user, and those which are for
developers only. If there's enough of the latter, we could ask the
sysfs people for a more flexible interface.
James
prev parent reply other threads:[~2003-12-01 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 10:36 Request for review of Linux iSCSI driver version 4.0.0.2 Naveen Burmi
2003-11-28 12:03 ` Christoph Hellwig
2003-12-01 10:46 ` Surekha.PC
2003-12-01 15:38 ` 'Christoph Hellwig'
2003-12-01 15:40 ` James Bottomley [this message]
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=1070293210.1778.25.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=davmyers@cisco.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=naveenb@cisco.com \
--cc=surekhap@cisco.com \
/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