From: "Matias Bjørling" <m@bjorling.me>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: axboe@kernel.dk, keith.busch@intel.com,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 0/3] Convert from bio-based to blk-mq v2
Date: Fri, 18 Oct 2013 21:10:22 +0200 [thread overview]
Message-ID: <5261879E.2020309@bjorling.me> (raw)
In-Reply-To: <20131018154801.GQ16716@linux.intel.com>
On 10/18/2013 05:48 PM, Matthew Wilcox wrote:
> On Fri, Oct 18, 2013 at 03:14:19PM +0200, Matias Bjorling wrote:
>> Performance study:
>>
>> System: HGST Research NVMe prototype, Haswell i7-4770 3.4Ghz, 32GB 1333Mhz
>
> I don't have one of these. Can you provide more details about it,
> such as:
> - How many I/O queues does it have?
> - Are the interrupts correctly bound to the CPUs (for both sets of tests)?
> The driver isn't allowed to set the irq affinity correctly itself;
> it can only set a hint and userspace (eg irqbalance) has to set the
> affinity correctly
> - Does it support interrupt coalescing? If so, have you managed to do any
> testing using that feature?
>
Current impletation is an PCI-e Gen2x4 interface, two I/O queues. One
for admin and one for all other I/Os. I'll check up on IRQ affinity when
multiple queues are available. I haven't yet tested interrupt coalescing.
next prev parent reply other threads:[~2013-10-18 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 13:14 [PATCH 0/3] Convert from bio-based to blk-mq v2 Matias Bjorling
2013-10-18 13:14 ` [PATCH 1/3] blk-mq: call exit_hctx on hw queue teardown Matias Bjorling
2013-10-18 13:14 ` [PATCH 2/3] NVMe: Extract admin queue size Matias Bjorling
2013-10-18 13:14 ` [PATCH 3/3] NVMe: Convert to blk-mq Matias Bjorling
2013-10-18 15:13 ` Keith Busch
2013-10-18 19:06 ` Matias Bjørling
2013-10-22 16:55 ` Keith Busch
2013-10-22 18:55 ` Matias Bjorling
2013-10-22 19:52 ` Keith Busch
2013-10-18 15:48 ` [PATCH 0/3] Convert from bio-based to blk-mq v2 Matthew Wilcox
2013-10-18 19:10 ` Matias Bjørling [this message]
2013-10-18 19:21 ` Matias Bjorling
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=5261879E.2020309@bjorling.me \
--to=m@bjorling.me \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=willy@linux.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