From: Mike Christie <michaelc@cs.wisc.edu>
To: "Surekha.PC" <surekhap@cisco.com>
Cc: 'SCSI Mailing List' <linux-scsi@vger.kernel.org>,
linux-iscsi-devel@lists.sourceforge.net
Subject: Re: [PATCH][RFC] iSCSI transport class
Date: Tue, 30 Mar 2004 13:02:04 -0800 [thread overview]
Message-ID: <4069E04C.2010102@cs.wisc.edu> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAANoIxZIFzbEaqwjJgytz2AeKAAAAQAAAA2gVe7Un3YUak/sHlj1pNxAEAAAAA@cisco.com>
Hey Surekha,
Thanks for the comments.
Surekha.PC wrote:
> Hi Mike,
>
> I have reviewed your changes for iSCSI transport class. The changes look
> fine.
> I have few suggestions on further improvements. The attributes can be
> organised
> under iSCSI transport class in the following structure.
>
> # ls /sys/class/iscsi_transport/*
>
> /* iSCSI host specific attributes */
> |-- shutdown
> |-- host_id
> |-- ....
The examples you placed here are not tranport specific. They are
just HBA values, and should stay under the host attributes.
Also, the host layout here does not look right. What happens when I
have multiple HBAs?
> /* iSCSI target specific attributes */
> |-- 1:0:1/
> |-- target_addr
> |-- target_name
> |-- target_port
> |-- ....
I agree these would be nice under a target attribute. Did
you have something to post since the last time we talked,
or did you write the example by hand?
> /* lun specific attributes */
> |-- 1:0:1:0/
> |-- device -> ../../../devices/platform/iscsi/1:0:0:0
> |-- driver -> ../../../bus/scsi/drivers/sd
> |-- lun_status
> |-- ....
I don't think anything in lun_status is iscsi specific.
> This way the relevant attributes can be used from respective paths.
>
I get your point (you just chose the above attributes based on
name to accentuate this right). However, in your example it seems
like you would want to show the parent-children relationships like
here:
/sys/class/iscsi_transport_host
|-- host1
| |-- a_host_attribute
| |-- 1:0:1
| | |-- target_name
| | |-- 1:0:1:0
| | | |- some_lun_attribute
Or you could also do something like
/sys/class/iscsi_transport_host
|-- host1
| |- a_host_attribute
| |- 1:0:1 -> ../iscsi_transport_target/1:0:1
| `- 1:0:2 -> ../iscsi_transport_target/1:0:2
/sys/class/iscsi_transport_target
|-- 1:0:1
| |- target_name
| |- ../iscsi_transport_lun/1:0:1:0
........
Making /sys/class/iscsi_transport the parent for everything just
does not look right.
Mike
next prev parent reply other threads:[~2004-03-30 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 20:50 [PATCH][RFC] iSCSI transport class Mike Christie
2004-03-30 14:21 ` Surekha.PC
2004-03-30 21:02 ` Mike Christie [this message]
2004-04-05 13:09 ` Surekha.PC
2004-04-05 20:22 ` Mike Christie
2004-04-05 21:10 ` Mike Christie
2004-04-06 8:36 ` Heiko Carstens
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=4069E04C.2010102@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--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