search for: scsi_get_host_dev

Displaying 5 results from an estimated 5 matches for "scsi_get_host_dev".

2020 Mar 11
6
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
...inux-scsi at vger.kernel.org/msg83177.html That was just a question on why virtio uses the per-device tags, which didn't look like it made any sense. What I'm worried about here is mixing up the concept of reserved tags in the tagset, and queues to use them. Note that we already have the scsi_get_host_dev to allocate a scsi_device and thus a request_queue for the host itself. That seems like the better interface to use a tag for a host wide command vs introducing a parallel path.
2020 Mar 11
6
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
...inux-scsi at vger.kernel.org/msg83177.html That was just a question on why virtio uses the per-device tags, which didn't look like it made any sense. What I'm worried about here is mixing up the concept of reserved tags in the tagset, and queues to use them. Note that we already have the scsi_get_host_dev to allocate a scsi_device and thus a request_queue for the host itself. That seems like the better interface to use a tag for a host wide command vs introducing a parallel path.
2020 Apr 07
0
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
...> That was just a question on why virtio uses the per-device tags, which >>> didn't look like it made any sense.? What I'm worried about here is >>> mixing up the concept of reserved tags in the tagset, and queues to use >>> them.? Note that we already have the scsi_get_host_dev to allocate >>> a scsi_device and thus a request_queue for the host itself.? That seems >>> like the better interface to use a tag for a host wide command vs >>> introducing a parallel path. >>> >> Thinking about it some more, I don't think that scsi_ge...
2020 Apr 07
0
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
...t;>>> host template; the device we'll be allocating would have basically >>>> nothing in common with the 'normal' SCSI devices. >>>> >>>> What we could do, though, is to try it the other way round: >>>> Lift the request queue from scsi_get_host_dev() into the scsi host >>>> itself, so that scsi_get_host_dev() can use that queue, but we also >>>> would be able to use it without a SCSI device attached. >>> >>> wouldn't that limit 1x scsi device per host, not that I know if any >>> more wou...
2020 Apr 23
0
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
On 4/23/20 4:13 PM, John Garry wrote: > On 07/04/2020 17:30, Christoph Hellwig wrote: >> On Tue, Apr 07, 2020 at 04:00:10PM +0200, Hannes Reinecke wrote: >>> My concern is this: >>> >>> struct scsi_device *scsi_get_host_dev(struct Scsi_Host *shost) >>> { >>> ????[ .. ] >>> ????starget = scsi_alloc_target(&shost->shost_gendev, 0, >>> shost->this_id); >>> ????[ .. ] >>> >>> and we have typically: >>> >>> drivers/scsi/hisi_sas/his...