From: Keith Busch <keith.busch@intel.com>
To: Dan Streetman <ddstreet@ieee.org>
Cc: Jens Axboe <axboe@fb.com>,
linux-nvme@lists.infradead.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Dan Streetman <dan.streetman@canonical.com>
Subject: Re: [PATCH] nvme: use the correct msix vector for each queue
Date: Wed, 7 Dec 2016 18:05:16 -0500 [thread overview]
Message-ID: <20161207230516.GB25959@localhost.localdomain> (raw)
In-Reply-To: <CALZtONAyqjK4RG0PAJJczzHkZrhzpvT2v9eUu3yXs949-Q51dg@mail.gmail.com>
On Wed, Dec 07, 2016 at 05:46:34PM -0500, Dan Streetman wrote:
>
> Is there a reason you want to share the interrupt between the queues?
The admin queue is hardly ever used (if at all) compared to an IO queue's
usage, so why waste the resource? I bet you can't measure a preformance
difference on queues that don't share, and it's reasonable to expect an
nvme controller's MSI-x count matches the IO queue count, which forces
us to share a vector.
prev parent reply other threads:[~2016-12-07 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 22:03 [PATCH] nvme: use the correct msix vector for each queue Dan Streetman
2016-12-07 22:44 ` Keith Busch
2016-12-07 22:36 ` Dan Streetman
2016-12-07 22:49 ` Keith Busch
2016-12-07 22:46 ` Christoph Hellwig
2016-12-07 22:49 ` Dan Streetman
2016-12-07 22:46 ` Dan Streetman
2016-12-07 23:05 ` Keith Busch [this message]
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=20161207230516.GB25959@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@fb.com \
--cc=dan.streetman@canonical.com \
--cc=ddstreet@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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