From: Mike Christie <michaelc@cs.wisc.edu>
To: open-iscsi@googlegroups.com, netdev <netdev@oss.sgi.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel@vger.kernel.org,
linux-iscsi-devel <linux-iscsi-devel@lists.sourceforge.net>
Subject: [PATCH 0/3] add open iscsi netlink interface to iscsi transport class
Date: Sun, 15 May 2005 12:29:39 -0700 [thread overview]
Message-ID: <4287A323.6010209@cs.wisc.edu> (raw)
The following patches add the linux-iscsi-5.X/open-iscsi project's
netlink interface to the iscsi transport class.
Last time I messed up and did not inline the patches so the reason for
the allignment in some structures was not clear. There was also a bug in
that unsigned long was being used instead of u64/unit64_t so that
complicated matters. We have been discussing this internally but I am
not sure I know the best route - I had hoped to just be able to remove
them all like was suggested, so I am reposting the patches inlined with
hopefully at least Chris Wright and almost all of Christoph Hellwig's
comments addressed.
The one suggestion we were not able to complete was the one to move the
scsi_remove_host and scsi_host_add calls. It is trivial to do, but
seemed odd since every iscsi_transport would need to add these calls. I
can understand in the future when HW iSCSI is supported all our
scsi_host lifetime code will need to be reworked because they allocate a
host per pci device and we allocate a host per session (maybe a common
place to meet would be a host per initiator port), but with only
software iSCSI supported today maybe a little more info is needed. Is
the suggestion to move the add/remove host calls to the iscsi_transport
to allow the transport to control when they want to begin queueing comamnds?
Maybe the removal of ISCSI_TRANSPORT_MAX is also not completely met too.
I am hoping to finish fixing that by exposing the same information
through sysfs, but I am still trying to figure out how the layout should
be implmented using the driver model transport classes and struct
devices or kobjects or whatever makes people happy. We could simply do
this using driver model transport classes by just adding a
iscsi_transport class that represents the iSCSI transport like
iscsi_tcp, iscsi_iser and making that the parent of the session, but
maybe that is better done in a seperate patch so we can discuss the
abstraction for the parent of the session seperately.
More info about the open-iscsi/linux-iscsi-5 project can found here
http://open-iscsi.org/.
Patches
1. add-iscsi-netlink-def.patch - include/linux/netlink.h changes (added
new protocol NETLINK_ISCSI)
2. common-iscsi-headers.patch - Common header files:
- iscsi_if.h (user/kernel #defines);
- iscsi_proto.h (RFC3720 #defines and types);
- iscsi_ifev.h (user/kernel events).
3. integrate-iscsi-netlink.patch - incorporate the
open-iscsi/linux-iscsi netlink interface into the iscsi transport class.
Thanks,
Linux-iscsi Team
next reply other threads:[~2005-05-15 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 19:29 Mike Christie [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-05 2:53 [PATCH 0/3] add open iscsi netlink interface to iscsi transport class Mike Christie
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=4287A323.6010209@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=open-iscsi@googlegroups.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;
as well as URLs for NNTP newsgroup(s).