All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: NVMe and IRQ Affinity
Date: Tue, 2 Feb 2016 23:58:19 +0000	[thread overview]
Message-ID: <20160202235818.GB21046@localhost.localdomain> (raw)
In-Reply-To: <CACo6K_YGiH2ER4s21OzmD69LDL+ES0PO54jJ_efcSFw7pHADvQ@mail.gmail.com>

On Wed, Feb 03, 2016@12:50:06AM +0100, Mark Jacobson wrote:
> Output is below. I'm aware the distro hints are fairly invalid.

They're all invalid. This kernel must have forked before the affinity
hints were fixed for a blk-mq nvme driver. A more optimal affinity hint
would match the mq's cpu_list, which is how it looks upstream.

I guess your platform strongly prefers CPU 0 when allowed. You can
either manually override the smp_affinity, use an out-of-tree driver
with a fix and let irqbalance handle it.

  reply	other threads:[~2016-02-02 23:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 23:31 NVMe and IRQ Affinity Mark Jacobson
2016-02-02 23:45 ` Keith Busch
2016-02-02 23:50   ` Mark Jacobson
2016-02-02 23:58     ` Keith Busch [this message]
2016-02-03  0:13       ` Mark Jacobson
2016-02-03 14:30         ` Keith Busch
2016-02-03 18:31           ` Azher Mughal
2016-02-03 18:58             ` Keith Busch
2016-02-03 16:14         ` Kim Kyungsan

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=20160202235818.GB21046@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.