From: "Love, Robert W" <robert.w.love@intel.com>
To: "axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Tomas Henzl <thenzl@redhat.com>, "Zou, Yi" <yi.zou@intel.com>
Subject: Re: [Resend PATCH v2] scsi_lib: rate-limit the error message from failing commands
Date: Fri, 25 May 2012 21:41:32 +0000 [thread overview]
Message-ID: <4FBFFC8C.3060301@intel.com> (raw)
In-Reply-To: <20120525212933.3366.51338.stgit@localhost6.localdomain6>
On 05/25/2012 02:29 PM, Robert Love wrote:
> From: Yi Zou <yi.zou@intel.com>
>
> When performing a cable pull test w/ active stress I/O using fio over
> a dual port Intel 82599 FCoE CNA, w/ 256LUNs on one port and about 32LUNs
> on the other, it is observed that the system becomes not usable due to
> scsi-ml being busy printing the error messages for all the failing commands.
> I don't believe this problem is specific to FCoE and these commands are
> anyway failing due to link being down (DID_NO_CONNECT), just rate-limit
> the messages here to solve this issue.
>
> v2->v1: use __ratelimit() as Tomas Henzl mentioned as the proper way for
> rate-limit per function. However, in this case, the failed i/o gets to
> blk_end_request_err() and then blk_update_request(), which also has to
> be rate-limited, as added in the v2 of this patch.
>
> Signed-off-by: Yi Zou <yi.zou@intel.com>
> Acked-by: Tomas Henzl <thenzl@redhat.com>
> Signed-off-by: Robert Love <robert.w.love@intel.com>
Hi Jens,
I think James may be waiting for an Ack from you before committing
this patch. The original patch submission wasn't sent to you. I'm just
resending so that it might get your attention.
Thanks, //Rob
prev parent reply other threads:[~2012-05-25 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 21:29 [Resend PATCH v2] scsi_lib: rate-limit the error message from failing commands Robert Love
2012-05-25 21:41 ` Love, Robert W [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=4FBFFC8C.3060301@intel.com \
--to=robert.w.love@intel.com \
--cc=axboe@kernel.dk \
--cc=linux-scsi@vger.kernel.org \
--cc=thenzl@redhat.com \
--cc=yi.zou@intel.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.