From: John Garry <john.g.garry@oracle.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: "Daniel Wagner" <wagi@kernel.org>, "Jens Axboe" <axboe@kernel.dk>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Keith Busch" <kbusch@kernel.org>,
"Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, virtualization@lists.linux.dev,
linux-scsi@vger.kernel.org, megaraidlinux.pdl@broadcom.com,
mpi3mr-linuxdrv.pdl@broadcom.com,
MPT-FusionLinux.pdl@broadcom.com, storagedev@microchip.com,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 1/8] driver core: bus: add irq_get_affinity callback to bus_type
Date: Wed, 13 Nov 2024 13:44:02 +0000 [thread overview]
Message-ID: <bed15207-c3d8-4e0b-b356-4880f5a4fdff@oracle.com> (raw)
In-Reply-To: <2d85aa5e-037a-45c3-9f2d-e46b2159b697@flourine.local>
On 13/11/2024 12:36, Daniel Wagner wrote:
>>> @@ -48,6 +48,7 @@ struct fwnode_handle;
>>> * will never get called until they do.
>>> * @remove: Called when a device removed from this bus.
>> My impression is that this would be better suited to "struct device_driver",
>> but I assume that there is a good reason to add to "struct bus_type".
> I think the main reason to put it here is that most of the drivers are
> happy with the getter on bus level and don't need special treatment. We
> don't have to touch all the drivers to hookup a common getter, nor do we
> have to install a default handler when the driver doesn't specify one.
> Having the callback in struct bus_driver avoids this. Though Christoph
> suggested it, so I can only guess.
>
> But you bring up a good point, if we had also an irq_get_affinity
> callback in struct device_driver it would be possible for the
> hisi_sas v2 driver to provide a getter and blk_mq_hctx_map_queues could
> do:
>
> for (queue = 0; queue < qmap->nr_queues; queue++) {
> if (dev->driver->irq_get_affinity)
> mask = dev->driver->irq_get_affinity;
> else if (dev->bus->irq_get_affinity)
> mask = dev->bus->irq_get_affinity(dev, queue + offset);
> if (!mask)
> goto fallback;
>
> for_each_cpu(cpu, mask)
> qmap->mq_map[cpu] = qmap->queue_offset + queue;
> }
>
> and with this in place the open coded version in hisi_sas v2 can also be
> replaced.
Yeah, I think that it could be plugged in like:
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index 342d75f12051..5172af77a3f0 100644
--- a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
+++ b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
@@ -3636,6 +3636,7 @@ static struct platform_driver hisi_sas_v2_driver = {
.name = DRV_NAME,
.of_match_table = sas_v2_of_match,
.acpi_match_table = ACPI_PTR(sas_v2_acpi_match),
+ .irq_get_affinity_mask = hisi_sas_v2_get_affinity_mask,
},
};
> If no one objects, I go ahead and add the callback to struct
> device_driver.
I'd wait for Christoph and Greg to both agree. I was just wondering why
we use bus_type.
next prev parent reply other threads:[~2024-11-13 13:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 13:26 [PATCH v3 0/8] blk: refactor queue affinity helpers Daniel Wagner
2024-11-12 13:26 ` [PATCH v3 1/8] driver core: bus: add irq_get_affinity callback to bus_type Daniel Wagner
2024-11-12 16:54 ` Christoph Hellwig
2024-11-13 9:46 ` Hannes Reinecke
2024-11-13 10:16 ` John Garry
2024-11-13 12:36 ` Daniel Wagner
2024-11-13 13:44 ` John Garry [this message]
2024-11-13 13:54 ` Greg Kroah-Hartman
2024-11-13 14:12 ` John Garry
2024-11-13 14:24 ` Greg Kroah-Hartman
2024-11-13 14:30 ` Christoph Hellwig
2024-11-12 13:26 ` [PATCH v3 2/8] PCI: hookup irq_get_affinity callback Daniel Wagner
2024-11-12 16:54 ` Christoph Hellwig
2024-11-13 9:47 ` Hannes Reinecke
2024-11-12 13:26 ` [PATCH v3 3/8] virtio: " Daniel Wagner
2024-11-12 16:55 ` Christoph Hellwig
2024-11-12 22:07 ` kernel test robot
2024-11-13 9:47 ` Hannes Reinecke
2024-11-12 13:26 ` [PATCH v3 4/8] blk-mp: introduce blk_mq_hctx_map_queues Daniel Wagner
2024-11-12 13:58 ` Greg Kroah-Hartman
2024-11-12 15:33 ` Daniel Wagner
2024-11-12 15:42 ` Greg Kroah-Hartman
2024-11-12 16:15 ` Daniel Wagner
2024-11-12 16:53 ` Greg Kroah-Hartman
2024-11-12 16:56 ` Christoph Hellwig
2024-11-12 18:25 ` Daniel Wagner
2024-11-13 9:48 ` Hannes Reinecke
2024-11-12 13:26 ` [PATCH v3 5/8] scsi: replace blk_mq_pci_map_queues with blk_mq_hctx_map_queues Daniel Wagner
2024-11-13 9:49 ` Hannes Reinecke
2024-11-13 10:09 ` John Garry
2024-11-12 13:26 ` [PATCH v3 6/8] nvme: " Daniel Wagner
2024-11-13 9:50 ` Hannes Reinecke
2024-11-12 13:26 ` [PATCH v3 7/8] virtio: blk/scsi: replace blk_mq_virtio_map_queues " Daniel Wagner
2024-11-13 9:51 ` Hannes Reinecke
2024-11-12 13:26 ` [PATCH v3 8/8] blk-mq: remove unused queue mapping helpers Daniel Wagner
2024-11-13 9:52 ` Hannes Reinecke
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=bed15207-c3d8-4e0b-b356-4880f5a4fdff@oracle.com \
--to=john.g.garry@oracle.com \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=dwagner@suse.de \
--cc=eperezma@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jasowang@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=mpi3mr-linuxdrv.pdl@broadcom.com \
--cc=mst@redhat.com \
--cc=sagi@grimberg.me \
--cc=storagedev@microchip.com \
--cc=virtualization@lists.linux.dev \
--cc=wagi@kernel.org \
--cc=xuanzhuo@linux.alibaba.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).