From: Ming Lei <ming.lei@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <kbusch@kernel.org>, Keith Busch <kbusch@meta.com>,
linux-nvme@lists.infradead.org, hch@lst.de
Subject: Re: [PATCHv2] nvme-pci: allow unmanaged interrupts
Date: Mon, 13 May 2024 09:12:58 +0800 [thread overview]
Message-ID: <ZkFpGlEMs4yHL+Xv@fedora> (raw)
In-Reply-To: <d6e8c980-7be7-4902-b466-79dc4b9beb17@grimberg.me>
On Sun, May 12, 2024 at 05:16:13PM +0300, Sagi Grimberg wrote:
>
> > > Everyone expects nvme performance will suffer. IO latency and CPU
> > > efficieny are not everyone's top priority, so allowing people to
> > > optimize for something else seems like a reasonable request.
> > I guess more people may be interested in 'something else', care to share
> > them in the commit log, cause nvme is going to support it.
>
> I don't have a special interest in this, but I can share what I heard
> several
> times. The use-case is that people want to dedicate a few cores to handle
> interrupts so they know it does not take cpu time from their application
> threads
> that are running (usually pinned to different cores).
>
> The app threads isolation is more important to them than affinity to the
> device...
That is exactly what CPU isolation is doing, include 'isolcpus=managed_irq',
isn't it?
Thanks,
Ming
next prev parent reply other threads:[~2024-05-13 1:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 17:46 [PATCHv2] nvme-pci: allow unmanaged interrupts Keith Busch
2024-05-10 23:47 ` Ming Lei
2024-05-11 0:29 ` Keith Busch
2024-05-11 0:44 ` Ming Lei
2024-05-12 14:16 ` Sagi Grimberg
2024-05-12 22:05 ` Keith Busch
2024-05-13 1:12 ` Ming Lei [this message]
2024-05-13 4:09 ` Keith Busch
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=ZkFpGlEMs4yHL+Xv@fedora \
--to=ming.lei@redhat.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--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