Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: IRQ and CPU Affinity on new Kernels
Date: Thu, 3 Dec 2015 23:50:41 +0000	[thread overview]
Message-ID: <20151203235041.GA3565@localhost.localdomain> (raw)
In-Reply-To: <CAMjVwgQRoPi8Chta3sXdxAZX3KCsQOu9fqRvL_i9qRqg1BkFmQ@mail.gmail.com>

On Thu, Dec 03, 2015@06:35:55PM -0500, Angelo Brito wrote:
> Hello Gentlemen,
> 
> We had some problems with a controller and some commands were missing
> (timeouts and cancelling I/O).
>
> I noticed that some interruptions were handled by different CPUs, like
> in this example:

I doubt the interrupt affinity you're seeing could have anything
to do with timeouts or missing commands.

There is a small window of time when a disk is initially brought online,
but before the affinity hints are provided. Because of that, even if
you properly affinitize all irqs to use the driver's hint, you'll likely
see a few irqs on non-optimal CPU.

  reply	other threads:[~2015-12-03 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 23:35 IRQ and CPU Affinity on new Kernels Angelo Brito
2015-12-03 23:50 ` Keith Busch [this message]
2015-12-04 15:19   ` Angelo Brito

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=20151203235041.GA3565@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox