From: azher@hep.caltech.edu (Azher Mughal)
Subject: NVMe and IRQ Affinity
Date: Wed, 3 Feb 2016 10:31:45 -0800 [thread overview]
Message-ID: <56B24791.7040807@hep.caltech.edu> (raw)
In-Reply-To: <20160203143055.GA23910@localhost.localdomain>
Hi Keith,
I have similar affinity issues in CentOS 7.2. The nvme module is generic
that came along with this distro. Is there a git repo which can be used
with the kernel "3.10.0-327.4.5" ?
Thanks
-Azher
# modinfo nvme
filename:
/lib/modules/3.10.0-327.4.5.el7.x86_64/kernel/drivers/block/nvme.ko
version: 1.0
license: GPL
author: Matthew Wilcox <willy at linux.intel.com>
rhelversion: 7.2
srcversion: 6FE34EC5F6A703F8EDE6C77
alias: pci:v*d*sv*sd*bc01sc08i02*
depends:
intree: Y
vermagic: 3.10.0-327.4.5.el7.x86_64 SMP mod_unload modversions
signer: CentOS Linux kernel signing key
sig_key: 10:5D:A1:3D:CA:AA:74:AE:50:00:17:E7:D5:2C:DA:9B:7C:C5:10:93
sig_hashalgo: sha256
parm: admin_timeout:timeout in seconds for admin commands (byte)
parm: io_timeout:timeout in seconds for I/O (byte)
parm: shutdown_timeout:timeout in seconds for controller
shutdown (byte)
parm: nvme_major:int
parm: nvme_char_major:int
parm: use_threaded_interrupts:int
On 2/3/2016 6:30 AM, Keith Busch wrote:
> On Wed, Feb 03, 2016@01:13:23AM +0100, Mark Jacobson wrote:
>> 1. When you say out-of-tree, do you mean a loadable kernel module?
>> (My understanding is that the NVMe driver is now part of the mainline
>> Linux kernel source tree, so I'm a bit confused as to where to nab
>> that from.)
> Yes, a loadable kernel module or a package that can build one. I am not
> aware of any publicly available. Perhaps your vendor provides one.
>
>> 2. Does the upstream 4.4.1 kernel have any of these fixes if I were to
>> build it myself with the appropriate support ticked off?
> The 4.3 kernel has the fixes, and anything newer than that should also
> work. I think it was just the 4.2 kernel that had this wrong (will see
> if there's are any stable patch candidates).
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>
next prev parent reply other threads:[~2016-02-03 18:31 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
2016-02-03 0:13 ` Mark Jacobson
2016-02-03 14:30 ` Keith Busch
2016-02-03 18:31 ` Azher Mughal [this message]
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=56B24791.7040807@hep.caltech.edu \
--to=azher@hep.caltech.edu \
/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