From: keith.busch@intel.com (Keith Busch)
Subject: Why NVMe MSIx vectors affinity set across NUMA nodes?
Date: Wed, 24 Jan 2018 08:48:42 -0700 [thread overview]
Message-ID: <20180124154841.GC14790@localhost.localdomain> (raw)
In-Reply-To: <CAKTKpr45pNcEtruqemwEm0uoDHizCJNNosiNbavz9+6LTttrVg@mail.gmail.com>
On Wed, Jan 24, 2018@07:47:44AM +0530, Ganapatrao Kulkarni wrote:
> application uses libnuma to align to numa locality.
> here the driver is breaking the affinity.
> certainly having affinity with remote node cpu will add latency to
> interrupt response time.
> here it is for some NVMe queues.
I bet you can't come up with an IRQ CPU affinity map that performs better
than the current setup.
next prev parent reply other threads:[~2018-01-24 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 4:25 Why NVMe MSIx vectors affinity set across NUMA nodes? Ganapatrao Kulkarni
2018-01-22 17:14 ` Keith Busch
2018-01-22 17:22 ` Ganapatrao Kulkarni
2018-01-22 17:32 ` Keith Busch
2018-01-22 17:55 ` Ganapatrao Kulkarni
2018-01-22 18:05 ` Keith Busch
2018-01-22 18:12 ` Ganapatrao Kulkarni
2018-01-22 18:20 ` Keith Busch
2018-01-23 13:30 ` Sagi Grimberg
2018-01-24 2:17 ` Ganapatrao Kulkarni
2018-01-24 15:48 ` Keith Busch [this message]
2018-01-24 19:39 ` Sagi Grimberg
2018-01-24 20:38 ` 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=20180124154841.GC14790@localhost.localdomain \
--to=keith.busch@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.