From: keith.busch@intel.com (Keith Busch)
Subject: [GIT PULL] nvme fix for 4.16-rc6
Date: Thu, 22 Mar 2018 16:02:25 -0600 [thread overview]
Message-ID: <20180322220224.GL12909@localhost.localdomain> (raw)
In-Reply-To: <71eda309-fa4a-7641-9292-fcc6c77d44af@kernel.dk>
On Thu, Mar 22, 2018@03:32:45PM -0600, Jens Axboe wrote:
> There seems to be some mismatch. nvme6q7 is 244:
>
> # cat /proc/irq/244/smp_affinity_list
> 49,51,53,55,57,59,61,63
>
> and 243 is nvme6q6:
>
> # cat /proc/irq/243/smp_affinity_list
> 17,19,21,23,41,43,45,47
>
> 244 has never triggered, if I do:
>
> # taskset -c 17 dd if=/dev/nvme6n1 of=/dev/null bs=4k iflag=direct count=1
>
> then look at interrupts, none of the nvme6 associated interrupts have
> triggered.
Thanks, got it now: blk_mq_pci_map_queues() doesn't take pre_vectors into
account, nor is there a way for it to know even about them. Some queues,
then, get interrupt affinity assigned to "possible" CPUs that aren't
online.
This approach will definitely need some more. Sorry for the trouble.
next prev parent reply other threads:[~2018-03-22 22:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 16:01 [GIT PULL] nvme fix for 4.16-rc6 Keith Busch
2018-03-16 16:14 ` Jens Axboe
2018-03-16 16:16 ` Christoph Hellwig
2018-03-16 16:26 ` Jens Axboe
2018-03-16 16:53 ` Keith Busch
2018-03-21 20:59 ` Keith Busch
2018-03-21 21:02 ` Jens Axboe
2018-03-21 21:44 ` Jens Axboe
2018-03-21 22:08 ` Keith Busch
2018-03-22 21:09 ` Keith Busch
2018-03-22 21:32 ` Jens Axboe
2018-03-22 22:02 ` Keith Busch [this message]
2018-03-22 22:09 ` Jens Axboe
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=20180322220224.GL12909@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