* [PATCH] nvme-pci: fix missed admin queue sq doorbell write @ 2026-04-21 16:18 ` Keith Busch 2026-04-22 6:01 ` Christoph Hellwig 2026-04-22 9:43 ` Kanchan Joshi 0 siblings, 2 replies; 4+ messages in thread From: Keith Busch @ 2026-04-21 16:18 UTC (permalink / raw) To: hch, linux-nvme; +Cc: joshi.k, Keith Busch From: Keith Busch <kbusch@kernel.org> We can batch admin commands, which means bd->last may be false, skipping the doorbell write so that we aggregate multiple commands per write. If a subsequent command can't be dispatched for whatever reason, we have to provide the blk-mq ops' commit_rqs callback in order to ensure we properly update the doorbell. Fixes: 58e5bdeb9c2b ("nvme: enable uring-passthrough for admin commands") Signed-off-by: Keith Busch <kbusch@kernel.org> --- drivers/nvme/host/pci.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c index db5fc9bf66272..4c052ed18cb8d 100644 --- a/drivers/nvme/host/pci.c +++ b/drivers/nvme/host/pci.c @@ -2241,6 +2241,7 @@ static int nvme_create_queue(struct nvme_queue *nvmeq, int qid, bool polled) static const struct blk_mq_ops nvme_mq_admin_ops = { .queue_rq = nvme_queue_rq, .complete = nvme_pci_complete_rq, + .commit_rqs = nvme_commit_rqs, .init_hctx = nvme_admin_init_hctx, .init_request = nvme_pci_init_request, .timeout = nvme_timeout, -- 2.52.0 ^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] nvme-pci: fix missed admin queue sq doorbell write 2026-04-21 16:18 ` [PATCH] nvme-pci: fix missed admin queue sq doorbell write Keith Busch @ 2026-04-22 6:01 ` Christoph Hellwig 2026-04-22 14:46 ` Keith Busch 2026-04-22 9:43 ` Kanchan Joshi 1 sibling, 1 reply; 4+ messages in thread From: Christoph Hellwig @ 2026-04-22 6:01 UTC (permalink / raw) To: Keith Busch; +Cc: hch, linux-nvme, joshi.k, Keith Busch On Tue, Apr 21, 2026 at 09:18:55AM -0700, Keith Busch wrote: > From: Keith Busch <kbusch@kernel.org> > > We can batch admin commands, which means bd->last may be false, How do we end up batching them? io_uring passthrough I guess? Can you expand the commit log a bit with that? Otherwise looks good: Reviewed-by: Christoph Hellwig <hch@lst.de> ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] nvme-pci: fix missed admin queue sq doorbell write 2026-04-22 6:01 ` Christoph Hellwig @ 2026-04-22 14:46 ` Keith Busch 0 siblings, 0 replies; 4+ messages in thread From: Keith Busch @ 2026-04-22 14:46 UTC (permalink / raw) To: Christoph Hellwig; +Cc: Keith Busch, linux-nvme, joshi.k On Wed, Apr 22, 2026 at 08:01:55AM +0200, Christoph Hellwig wrote: > On Tue, Apr 21, 2026 at 09:18:55AM -0700, Keith Busch wrote: > > From: Keith Busch <kbusch@kernel.org> > > > > We can batch admin commands, which means bd->last may be false, > > How do we end up batching them? io_uring passthrough I guess? Can > you expand the commit log a bit with that? Exactly, io_uring_cmd passthrough starts a plug. The "Fixes" tag is a bit subtle, so I'll more explicitly state this in the commit message. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] nvme-pci: fix missed admin queue sq doorbell write 2026-04-21 16:18 ` [PATCH] nvme-pci: fix missed admin queue sq doorbell write Keith Busch 2026-04-22 6:01 ` Christoph Hellwig @ 2026-04-22 9:43 ` Kanchan Joshi 1 sibling, 0 replies; 4+ messages in thread From: Kanchan Joshi @ 2026-04-22 9:43 UTC (permalink / raw) To: Keith Busch, hch, linux-nvme; +Cc: Keith Busch Thanks. Reviewed-by: Kanchan Joshi <joshi.k@samsung.com> ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-04-22 14:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CGME20260421162015epcas5p3ba67958507806dd09025a2a85b3ddf89@epcas5p3.samsung.com>
2026-04-21 16:18 ` [PATCH] nvme-pci: fix missed admin queue sq doorbell write Keith Busch
2026-04-22 6:01 ` Christoph Hellwig
2026-04-22 14:46 ` Keith Busch
2026-04-22 9:43 ` Kanchan Joshi
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox