From: Jeff Johnson <jeff.johnson@aeoncomputing.com>
To: linux-nvme@lists.infradead.org
Subject: Pinning nvme interrupts to a single cpu?
Date: Mon, 27 Apr 2020 17:10:47 -0700 [thread overview]
Message-ID: <CAFCYAscnovJyA0cKeHVxS20+zGgMj4P5ECb95aZE8=o=Wh+5bg@mail.gmail.com> (raw)
Greetings,
Is it possible to limit nvme interrupts to a single cpu, rather than
spread them across many? I have a latency sensitive workload and I am
trying to do the opposite of what many appear to be doing, I need to
assign interrupts to a small number of cpus (one for nvme, one for
Ethernet, etc) leaving the bulk of my cpus for the application.
Single nvme drive which is both boot and application local storage.
Performance is nice but in my case it's more important to pin the
interrupts to one cpu even if local nvme performance decreases.
Thx,
--Jeff
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-04-28 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 0:10 Jeff Johnson [this message]
2020-04-28 3:37 ` Pinning nvme interrupts to a single cpu? Keith Busch
2020-04-28 3:46 ` Ming Lei
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='CAFCYAscnovJyA0cKeHVxS20+zGgMj4P5ECb95aZE8=o=Wh+5bg@mail.gmail.com' \
--to=jeff.johnson@aeoncomputing.com \
--cc=linux-nvme@lists.infradead.org \
/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).