From: Tero Kristo <tero.kristo@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk,
linux-nvme@lists.infradead.org, sagi@grimberg.me,
kbusch@kernel.org
Subject: Re: [PATCH 1/1] nvme-pci: Add CPU latency pm-qos handling
Date: Wed, 09 Oct 2024 09:45:07 +0300 [thread overview]
Message-ID: <913b063d0638614bc95d92969879d2096ffc0722.camel@linux.intel.com> (raw)
In-Reply-To: <20241007061926.GA800@lst.de>
On Mon, 2024-10-07 at 08:19 +0200, Christoph Hellwig wrote:
> > @@ -483,6 +498,27 @@ static inline void nvme_write_sq_db(struct
> > nvme_queue *nvmeq, bool write_sq)
> > nvmeq->dbbuf_sq_db, nvmeq->dbbuf_sq_ei))
> > writel(nvmeq->sq_tail, nvmeq->q_db);
> > nvmeq->last_sq_tail = nvmeq->sq_tail;
> > +
> > + /* Kick CPU latency while updating queue. */
> > + dev = nvmeq->dev;
> > + if (!dev || dev->cpu_latency < 0)
> > + return;
> > +
> > + for_each_cpu(cpu, nvmeq->irq_aff_mask) {
>
> Doing something as complex as this for every doorbell write is not
> going to fly.
>
> Even if it was I see nothing nvme-specific in the interface.
>
> So please figure out a way to make things cheap in the I/O path
> and move code to the right layers.
Initially, I posted the patch against block layer, but there the
recommendation was to move this closer to the HW; i.e. NVMe driver
level.
See:
https://patchwork.kernel.org/project/linux-block/patch/20240829075423.1345042-2-tero.kristo@linux.intel.com/
Any tips where this piece of code should actually be moved would be
appreciated.
-Tero
>
> Also please avoid all these overly long lines.
next prev parent reply other threads:[~2024-10-09 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 10:09 [PATCH 0/1] nvme-pci: Add CPU latency pm-qos handling Tero Kristo
2024-10-04 10:09 ` [PATCH 1/1] " Tero Kristo
2024-10-07 6:19 ` Christoph Hellwig
2024-10-09 6:45 ` Tero Kristo [this message]
2024-10-09 8:00 ` Christoph Hellwig
2024-10-09 8:24 ` Tero Kristo
2024-10-15 9:25 ` Tero Kristo
2024-10-15 13:29 ` Christoph Hellwig
2024-10-18 7:58 ` Tero Kristo
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=913b063d0638614bc95d92969879d2096ffc0722.camel@linux.intel.com \
--to=tero.kristo@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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