From: Jayamohan Kallickal <jayamohank@serverengines.com>
To: linux-scsi@vger.kernel.org
Cc: James.Bottomley@suse.de, michaelc@cs.wisc.edu
Subject: be2iscsi driver
Date: Sat, 5 Sep 2009 07:32:50 +0530 [thread overview]
Message-ID: <20090905020231.GA11756@serverengines.com> (raw)
Hi
Thanks to John Stoffel for the review.
This patch takes care of the concern raised by Mike Christie that if an
allocation fails then a lower size is not tried.
I request you to pl consider this for inclusion
in the Linux Kernel.
This patch supports blk-iopoll and is pulled from Jens Axboe's tree at
git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git
blk-iopoll
The ServerEngines be2iscsi driver works in Full Hardware Offload
mode utilizing the hooks provided by open-iscsi layer.
The series of patches are described below:
[PATCH 1/8]: The completion of IO's is done using a different path
[PATCH 2/8]: Adding checks for iscsi_queuecommand/xmit_task to handle
Tx Suspended state.
[PATCH 3/8]: Modified scsi Layer and be2iscsi Makefile/Kconfig
to add be2iscsi
[PATCH 4/8]: This file contains all routines for Initiallization/Teardown,
registering with upper layer, IO Handling, allocation/free etc.
[PATCH 5/8]: These are the low level routines to talk to the chip for
Management commands.
[PATCH 6/8]: The iscsi hooks to interact with open-iscsi layer.
[PATCH 7/8]: The Firmware Commands that are used for Management action
like setup /tear down a connection etc.
[PATCH 8/8]: The modified MAINTAINERS file with be2iscsi added.
Thank You
Jayamohan Kallickal
Signed-off-by: Jayamohan Kallickal <jayamohank@serverengines.com>
---
next reply other threads:[~2009-09-05 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 2:02 Jayamohan Kallickal [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-08 8:35 be2iscsi driver Jayamohan Kallickal
2009-09-08 10:06 ` Stephen Rothwell
2009-09-08 14:18 ` James Bottomley
2009-09-02 4:06 Jayamohan Kallickal
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=20090905020231.GA11756@serverengines.com \
--to=jayamohank@serverengines.com \
--cc=James.Bottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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