From: Karen Xie <kxie@chelsio.com>
To: open-iscsi@googlegroups.com, linux-scsi@vger.kernel.org
Cc: michaelc@cs.wisc.edu, James.Bottomley@HansenPartnership.com,
kxie@chelsio.com
Subject: [PATCH 0/2 2.6.29-rc] cxgb3i -- handles chip reset
Date: Tue, 24 Feb 2009 17:28:09 -0800 [thread overview]
Message-ID: <200902250128.n1P1S9IC007732@localhost.localdomain> (raw)
[PATCH 0/2 2.6.29-rc] cxgb3i -- handling of chip reset
From: Karen Xie <kxie@chelsio.com>
The following patches added support of the cxgb3 chip reset. The reset could
happen due to EEH event or a fatal error. The cxgb3i would re-initialize the
hardware and its offload function. The iscsi error recovery mechanism will
re-establish the tcp connection after reset.
The patches are based on scsi-rc-fixes-2.6 git.
The cxgb3i portion of the patch requires the the following cxgb3 patch in the
linux-next git tree:
(http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commitdiff;h=cb0bc205959bf8c60acae9c71f3da0597e756f8e).
Thanks.
Karen
reply other threads:[~2009-02-25 1:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200902250128.n1P1S9IC007732@localhost.localdomain \
--to=kxie@chelsio.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--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