From: David C Somayajulu <david.somayajulu@qlogic.com>
To: James Bottomley <James.Bottomley@SteelEye.com>,
linux-scsi@vger.kernel.org
Cc: open-iscsi@googlegroups.com, Mike Christie <michaelc@cs.wisc.edu>,
Doug Maxey <dwm@enoyolf.org>,
David Wagner <david.wagner@qlogic.com>,
David Somayajulu <david.somayajulu@qlogic.com>,
Ravi Anand <ravi.anand@qlogic.com>,
Duane Grigsby <duane.grigsby@qlogic.com>
Subject: [RFC] [PATCH] qla4xxx driver resubmission
Date: Tue, 19 Sep 2006 17:08:07 -0700 [thread overview]
Message-ID: <1158710887.4358.17.camel@dcslnxpc.site> (raw)
This is another resubmission of qla4xxx driver for QLogic Corporation's iSCSI HBAs.
The main changes from the previous submission are
- use block layer tagging
- clean up code and remove unused function for firmware pass thru
Please not that this patch is dependant on the previously posted patch titled
[RFC] [PATCH] helper function for retrieving scsi_cmd given host based block layer tag
( http://marc.theaimsgroup.com/?l=linux-scsi&m=115871027627964&w=2 )
The complete mega patch for the driver is at
ftp://ftp.qlogic.com/outgoing/linux/iSCSI/upstream/5.00.05b10-k/0000-Initial-Commit-qla4xxx.txt
For ease of comprehension the above patch has been broken down into
the following smaller patches:
(located at ftp://ftp.qlogic.com/outgoing/linux/iSCSI/upstream/5.00.05b10-k/ )
0001-qla4xxx-driver-defs.diff
0002-qla4xxx-driver-init.diff
0003-qla4xxx-driver-os.diff
0004-qla4xxx-driver-isr.diff
0005-qla4xxx-driver-mbx.diff
0006-qla4xxx-driver-support.diff
0007-qla4xxx-driver-version.diff
All patches are against scsi-misc-2.6.git
Other items which needs to be done are
- Add support for sysfs attributes.
- Userspace support for session creation/deletion for iscsi HBAs.
- Add support for other discovery modes ie iSNS/SLP.
Here are the links to the previous two submissions
http://marc.theaimsgroup.com/?l=linux-scsi&m=115532714515853&w=2
http://groups.google.com/group/open-iscsi/browse_frm/thread/536ce2edf9a60c48?hl=en
I believe block layer tagging was the gating item in the last submission.
I would really appreciate if it can be merged upstream.
Regards,
David Somayajulu
Qlogic Corporation.
next reply other threads:[~2006-09-20 0:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 0:08 David C Somayajulu [this message]
2006-09-21 13:46 ` [RFC] [PATCH] qla4xxx driver resubmission James Smart
2006-09-21 17:35 ` David Somayajulu
2006-09-21 18:11 ` James Smart
2006-09-21 18:35 ` Mike Christie
2006-09-21 18:25 ` Mike Christie
2006-09-21 18:35 ` Jens Axboe
2006-09-21 18:37 ` Mike Christie
2006-09-21 18:45 ` Jens Axboe
2006-09-21 18:47 ` Jens Axboe
2006-09-21 18:55 ` David Somayajulu
2006-09-21 19:00 ` Jens Axboe
2006-09-25 16:56 ` David Somayajulu
2006-09-30 0:42 ` David Somayajulu
2006-10-04 15:49 ` James Bottomley
2006-10-04 16:30 ` David Somayajulu
2006-10-04 16:39 ` James Bottomley
2006-10-04 16:44 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 18:30 David Somayajulu
2006-07-27 19:11 ` David C Somayajulu
2006-07-27 22:09 ` Doug Maxey
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=1158710887.4358.17.camel@dcslnxpc.site \
--to=david.somayajulu@qlogic.com \
--cc=James.Bottomley@SteelEye.com \
--cc=david.wagner@qlogic.com \
--cc=duane.grigsby@qlogic.com \
--cc=dwm@enoyolf.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=open-iscsi@googlegroups.com \
--cc=ravi.anand@qlogic.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