Displaying 3 results from an estimated 3 matches for "scsi_get_reserved_cmd".
2020 Apr 23
0
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
...e exposed anywhere.? And I prefer that over having
>> magic requests/scsi_cmnd that do not have a valid ->device pointer.
>> .
>>
>
> (just looking at this again)
>
> Hi Christoph,
>
> So how would this look added in scsi_lib.c:
>
> struct scsi_cmnd *scsi_get_reserved_cmd(struct Scsi_Host *shost)
> {
> ????struct scsi_cmnd *scmd;
> ????struct request *rq;
> ????struct scsi_device *sdev = scsi_get_host_dev(shost);
>
> ????if (!sdev)
> ??????? return NULL;
>
> ????rq = blk_mq_alloc_request(sdev->request_queue,
> ??????????????...
2020 Mar 11
6
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
On Tue, Mar 10, 2020 at 09:08:56PM +0000, John Garry wrote:
> On 10/03/2020 18:32, Christoph Hellwig wrote:
> > On Wed, Mar 11, 2020 at 12:25:28AM +0800, John Garry wrote:
> > > From: Hannes Reinecke <hare at suse.com>
> > >
> > > Allocate a separate 'reserved_cmd_q' for sending reserved commands.
> >
> > Why? Reserved command
2020 Mar 11
6
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
On Tue, Mar 10, 2020 at 09:08:56PM +0000, John Garry wrote:
> On 10/03/2020 18:32, Christoph Hellwig wrote:
> > On Wed, Mar 11, 2020 at 12:25:28AM +0800, John Garry wrote:
> > > From: Hannes Reinecke <hare at suse.com>
> > >
> > > Allocate a separate 'reserved_cmd_q' for sending reserved commands.
> >
> > Why? Reserved command