public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: James Bottomley <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Doug Ledford <dledford@redhat.com>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Max Gurtovoy <maxg@mellanox.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH 0/2] SRP transport, scsi-mq: Wait for .queue_rq() if necessary
Date: Fri, 25 Nov 2016 10:12:14 -0500	[thread overview]
Message-ID: <yq1d1hjtwz5.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <39d8cb23-0406-e8c3-6e3a-a467ebe41470@sandisk.com> (Bart Van Assche's message of "Tue, 22 Nov 2016 16:16:06 -0800")

>>>>> "Bart" == Bart Van Assche <bart.vanassche@sandisk.com> writes:

Bart> The SRP transport code must wait until ongoing .queuecommand() /
Bart> .queue_rq() callback function invocations have finished before
Bart> reconnecting at the transport layer level and also before invoking
Bart> .terminate_rport_io(). This is already the case for the single
Bart> queue path but not yet for the scsi-mq path. This patch series
Bart> realizes the proper serialization for the scsi-mq path. Compared
Bart> to last time these patches were posted, only the patch
Bart> descriptions and one comment have been changed.

Applied to 4.10/scsi-queue.

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2016-11-25 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23  0:16 [PATCH 0/2] SRP transport, scsi-mq: Wait for .queue_rq() if necessary Bart Van Assche
     [not found] ` <39d8cb23-0406-e8c3-6e3a-a467ebe41470-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-11-23  0:17   ` [PATCH 1/2] SRP transport: Move queuecommand() wait code to SCSI core Bart Van Assche
2016-11-25 23:21     ` Max Gurtovoy
2016-11-29 14:59       ` Bart Van Assche
     [not found]         ` <BLUPR02MB16836EF63187DE03E7F1DD77818D0-Y8PPn9RqzNfZ9ihocuPUdanrV9Ap65cLvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-11-29 16:22           ` Martin K. Petersen
2016-11-23  0:17   ` [PATCH 2/2] SRP transport, scsi-mq: Wait for .queue_rq() if necessary Bart Van Assche
2016-12-16 12:39     ` Bart Van Assche
2016-12-20 22:14       ` Martin K. Petersen
2016-11-25 15:12 ` Martin K. Petersen [this message]
2016-11-25 15:19   ` [PATCH 0/2] " Martin K. Petersen

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=yq1d1hjtwz5.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=dledford@redhat.com \
    --cc=hch@lst.de \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=maxg@mellanox.com \
    --cc=sagi@grimberg.me \
    /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