public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasu Dev <vasu.dev@linux.intel.com>
To: "Nicholas A. Bellinger" <nab@daterainc.com>
Cc: target-devel <target-devel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	fcoe-devel <fcoe-devel@open-fcoe.org>,
	Nicholas Bellinger <nab@linux-iscsi.org>
Subject: Re: [PATCH 0/2] tcm_fc: Generate TASK_SET_FULL for DataIN + response failures
Date: Fri, 06 Jun 2014 13:38:41 -0700	[thread overview]
Message-ID: <1402087121.5752.91.camel@vi-devel> (raw)
In-Reply-To: <1402011002-20771-1-git-send-email-nab@daterainc.com>

On Thu, 2014-06-05 at 23:30 +0000, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger <nab@linux-iscsi.org>
> 
> Hi Vasu,
> 
> This series generates SAM_STAT_TASK_SET_FULL status for lport->tt.seq_send()
> failures in DataIN + response status codepaths, which is done in order to get
> the initiator to reduce it's current queue_depth thus reducing the number of
> outstanding I/Os permitted in flight on the wire.
> 
> For the DataIN case, once a lport->tt.seq_send() failure occurs it will stop
> attempting to send subsequent DataIN payload data, and immediately attempt to
> send a response packet with SAM_STAT_TASK_SET_FULL status.
> 
> For the response case, once a lport->tt.seq_send() failure occurs it will
> set SAM_STAT_TASK_SET_FULL status and return -ENOMEM to the target, forcing
> the response to be requeued by target-core
> 

Good change and it was missing in tcm_fc.

> Note this series has been compile tested only, so please review + test.

Just did review and basic test but should be stressed to really ensure
it does work & fixes issues resulting these patches.

Thanks,
Vasu

> Thank you,
> 
> --nab
> 
> Nicholas Bellinger (2):
>   tcm_fc: Generate TASK_SET_FULL status for DataIN failures
>   tcm_fc: Generate TASK_SET_FULL status for response failures
> 
>  drivers/target/tcm_fc/tfc_cmd.c |   19 ++++++++++++++++---
>  drivers/target/tcm_fc/tfc_io.c  |   14 +++++++++++++-
>  2 files changed, 29 insertions(+), 4 deletions(-)
> 

  parent reply	other threads:[~2014-06-06 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 23:30 [PATCH 0/2] tcm_fc: Generate TASK_SET_FULL for DataIN + response failures Nicholas A. Bellinger
2014-06-05 23:30 ` [PATCH 1/2] tcm_fc: Generate TASK_SET_FULL status for DataIN failures Nicholas A. Bellinger
2014-06-06 20:51   ` Vasu Dev
2014-06-06 21:02     ` Nicholas A. Bellinger
2014-06-09 17:19       ` Vasu Dev
2014-06-05 23:30 ` [PATCH 2/2] tcm_fc: Generate TASK_SET_FULL status for response failures Nicholas A. Bellinger
     [not found]   ` <1402011002-20771-3-git-send-email-nab-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
2014-06-06 21:03     ` Vasu Dev
2014-06-06 21:11       ` Nicholas A. Bellinger
2014-06-09 17:16         ` Vasu Dev
2014-06-06 20:38 ` Vasu Dev [this message]
2014-06-06 21:09   ` [PATCH 0/2] tcm_fc: Generate TASK_SET_FULL for DataIN + " Nicholas A. Bellinger
2014-06-09 17:13     ` Vasu Dev

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=1402087121.5752.91.camel@vi-devel \
    --to=vasu.dev@linux.intel.com \
    --cc=fcoe-devel@open-fcoe.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@daterainc.com \
    --cc=nab@linux-iscsi.org \
    --cc=target-devel@vger.kernel.org \
    /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