The block layer already has the notion of 'reserved' commands, so
we should be enabling hosts to allocate them.
Signed-off-by: Hannes Reinecke
---
drivers/scsi/scsi_lib.c | 1 +
include/scsi/scsi_host.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi
On Fri, Feb 17, 2017 at 09:23:09AM +0100, Hannes Reinecke wrote:
> The block layer already has the notion of 'reserved' commands, so
> we should be enabling hosts to allocate them.
How does this interact with the non blk-mq path?
On 02/17/2017 09:55 AM, Christoph Hellwig wrote:
> On Fri, Feb 17, 2017 at 09:23:09AM +0100, Hannes Reinecke wrote:
>> The block layer already has the notion of 'reserved' commands, so
>> we should be enabling hosts to allocate them.
>
> How does this interact with the non blk-mq path?
>
It doesn
On Fri, Feb 17, 2017 at 10:00:28AM +0100, Hannes Reinecke wrote:
> So here's my question: how are 'reserved' commands are imagined to be used?
> ATM they exist for blk-mq solely, and are not even implemented for
> legacy sq.
Yes.
> At the same time quite some drivers (like mpt3sas) really could m
4 matches
Mail list logo