From: James Smart <james.smart@emulex.com>
To: "michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2/2] lpfc: block target when port queueing limit is hit
Date: Fri, 25 Feb 2011 19:07:54 -0500 [thread overview]
Message-ID: <4D68445A.1080707@emulex.com> (raw)
In-Reply-To: <1298664268-12967-3-git-send-email-michaelc@cs.wisc.edu>
Acked-by: James Smart <james.smart@emulex.com>
-- james s
On 2/25/2011 3:04 PM, michaelc@cs.wisc.edu wrote:
> From: Mike Christie<michaelc@cs.wisc.edu>
>
> Instead of blocking the entire host when the port's
> queueing limit is hit, we should only block the port's
> target. This will allow IO to other ports to execute.
>
> Signed-off-by: Mike Christie<michaelc@cs.wisc.edu>
> ---
> drivers/scsi/lpfc/lpfc_scsi.c | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/lpfc/lpfc_scsi.c b/drivers/scsi/lpfc/lpfc_scsi.c
> index af5aaaa..63a81a4 100644
> --- a/drivers/scsi/lpfc/lpfc_scsi.c
> +++ b/drivers/scsi/lpfc/lpfc_scsi.c
> @@ -3008,7 +3008,7 @@ lpfc_queuecommand_lck(struct scsi_cmnd *cmnd, void (*done) (struct scsi_cmnd *))
> goto out_fail_command;
> }
> if (atomic_read(&ndlp->cmd_pending)>= ndlp->cmd_qdepth)
> - goto out_host_busy;
> + goto out_tgt_busy;
>
> lpfc_cmd = lpfc_get_scsi_buf(phba, ndlp);
> if (lpfc_cmd == NULL) {
> @@ -3125,6 +3125,9 @@ lpfc_queuecommand_lck(struct scsi_cmnd *cmnd, void (*done) (struct scsi_cmnd *))
> out_host_busy:
> return SCSI_MLQUEUE_HOST_BUSY;
>
> + out_tgt_busy:
> + return SCSI_MLQUEUE_TARGET_BUSY;
> +
> out_fail_command:
> done(cmnd);
> return 0;
prev parent reply other threads:[~2011-02-26 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 20:04 lpfc fixes for 2.6.39 michaelc
2011-02-25 20:04 ` [PATCH 1/2] lpfc: force retry in queuecommand when port is transitioning michaelc
2011-02-26 0:07 ` James Smart
2011-02-25 20:04 ` [PATCH 2/2] lpfc: block target when port queueing limit is hit michaelc
2011-02-26 0:07 ` James Smart [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=4D68445A.1080707@emulex.com \
--to=james.smart@emulex.com \
--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 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.