linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: John Garry <john.garry@huawei.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Subject: Re: [PATCH RFC 00/24] scsi: enable reserved commands for LLDDs
Date: Mon, 9 Mar 2020 14:57:03 +0100	[thread overview]
Message-ID: <65727403-a390-795f-08ce-581ed4e3f3c2@suse.de> (raw)
In-Reply-To: <801604cd-d51f-2a4a-0e68-b6fcff9c9974@huawei.com>

On 3/9/20 1:48 PM, John Garry wrote:
> On 23/08/2019 14:26, John Garry wrote:
>>>
>>> quite some drivers use internal commands for various purposes, most
>>> commonly sending TMFs or querying the HBA status.
>>> While these commands use the same submission mechanism than normal
>>> I/O commands, they will not be counted as outstanding commands,
>>> requiring those drivers to implement their own mechanism to figure
>>> out outstanding commands.
>>> This patchset enables the use of reserved tags for the SCSI midlayer,
>>> enabling LLDDs to rely on the block layer for tracking outstanding
>>> commands.
>>> More importantly, it allows LLDD to request a valid tag from the block
>>> layer without having to implement some tracking mechanism within the
>>> driver. This removes quite some hacks which were required for some
>>> drivers (eg. fnic or snic).
>>>
>>> As usual, comments and reviews are welcome.
>>>
>>
> Hi Hannes,
> 
> JFYI, I have rebased this series to 5.6-rc4 here:
> 
> https://github.com/hisilicon/kernel-dev/tree/private-topic-sas-5.6-resv-commands-v1
> 
> 
> I am interested in enabling this for libsas and associated HBAs, so
> there are some patches on top for that.
> 
> No review comments have been addressed, apart from removing "block:
> disable elevator for reserved tags"
> 
> Please let me know your plan for this series.
> 
The plan is to wait for the shared tagset patchset to go in first :-)

Without it we'll be running on one tag bitmap per queue, and we risk
duplicate tags when sending down reserved commands :-(

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		           Kernel Storage Architect
hare@suse.de			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer

  reply	other threads:[~2020-03-09 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190529132901.27645-1-hare@suse.de>
2019-08-23 13:26 ` [PATCH RFC 00/24] scsi: enable reserved commands for LLDDs John Garry
2019-08-26 15:27   ` Hannes Reinecke
2019-09-02  8:47     ` John Garry
2019-09-09 15:11       ` Hannes Reinecke
2020-03-09 12:48   ` John Garry
2020-03-09 13:57     ` Hannes Reinecke [this message]
2020-03-09 14:21       ` John Garry
2020-03-10  8:43         ` John Garry

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=65727403-a390-795f-08ce-581ed4e3f3c2@suse.de \
    --to=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=john.garry@huawei.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).