From: Mike Christie <michaelc@cs.wisc.edu>
To: open-iscsi@googlegroups.com
Cc: Anil Veerabhadrappa <anilgv@broadcom.com>,
James B <James.Bottomley@suse.de>,
linux scsi <linux-scsi@vger.kernel.org>
Subject: Re: [RESEND PATCH] BNX2I - Bug fixes related to MTU change issue when there are active iscsi sessions
Date: Thu, 08 Apr 2010 21:32:19 -0500 [thread overview]
Message-ID: <4BBE91B3.5070705@cs.wisc.edu> (raw)
In-Reply-To: <1270767555.28522.109818.camel@anilgv-desktop>
On 04/08/2010 05:59 PM, Anil Veerabhadrappa wrote:
> James,
> Please apply this patch to fix resources leak issue when device MTU
> is changed or ethtool selftest is executed while there are active iscsi
> sessions.
>
> Thanks,
> Anil
>
>
> * bnx2i driver has to wait and cleanup all iscsi endpoints before
> returning from bnx2i_stop(). This is to make sure all chip
> resources are freed before chip is reset.
> * As the requirements for 1G and 10G chipsets is different, added
> per-device 'hba_shutdown_tmo' parameter to adapter structure
> * If the connections are not torn down by the daemon within this
> timeout period, 'cid's will be leaked in 10G device. 1G devices
> are more flexible and do not leak any resources because the whole
> chip ports gets reset when MTU is changed or ethtool selftest is run
> * fixed a minor issue in bnx2i_ep_poll() which unnecessarily forced
> error return code when driver timed out waiting for TCP connect
> request to complete
>
> Signed-off-by: Anil Veerabhadrappa<anilgv@broadcom.com>
Looks ok now.
Reviewed-by: Mike Christie <michaelc@cs.wisc.edu>
prev parent reply other threads:[~2010-04-09 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 22:59 [RESEND PATCH] BNX2I - Bug fixes related to MTU change issue when there are active iscsi sessions Anil Veerabhadrappa
2010-04-09 2:32 ` Mike Christie [this message]
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=4BBE91B3.5070705@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@suse.de \
--cc=anilgv@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.