linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Hannes Reinecke <hare@suse.de>,
	"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 12:48:41 +0000	[thread overview]
Message-ID: <801604cd-d51f-2a4a-0e68-b6fcff9c9974@huawei.com> (raw)
In-Reply-To: <e5c2b01a-71d9-ef94-3bf6-0830d866e4cf@huawei.com>

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.

Thanks,
John

> 
> I was wondering if you have any plans to progress this series?
> 
> I don't mind helping out...
> 
> Cheers,
> John
> 
>> Hannes Reinecke (24):
>>   block: disable elevator for reserved tags
>>   scsi: add scsi_{get,put}_reserved_cmd()
>>   scsi: add 'nr_reserved_cmds' field to the SCSI host template
>>   csiostor: use reserved command for LUN reset
>>   scsi: add scsi_cmd_from_priv()
>>   virtio_scsi: use reserved commands for TMF
>>   scsi: add host tagset busy iterator
>>   fnic: use reserved commands
>>   fnic: use scsi_host_tagset_busy_iter() to traverse commands
>>   scsi: allocate separate queue for reserved commands
>>   scsi: add scsi_host_get_reserved_cmd()
>>   hpsa: move hpsa_hba_inquiry after scsi_add_host()
>>   hpsa: use reserved commands 


  parent reply	other threads:[~2020-03-09 12:48 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 [this message]
2020-03-09 13:57     ` Hannes Reinecke
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=801604cd-d51f-2a4a-0e68-b6fcff9c9974@huawei.com \
    --to=john.garry@huawei.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.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).