From: Jens Axboe <axboe@kernel.dk>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ming Lei <tom.leiming@gmail.com>
Subject: Re: blk-mq: bitmap tag: performance degradation?
Date: Thu, 05 Jun 2014 08:03:01 -0600 [thread overview]
Message-ID: <53907895.8090102@kernel.dk> (raw)
In-Reply-To: <20140605140127.GA22198@dhcp-26-207.brq.redhat.com>
On 2014-06-05 08:01, Alexander Gordeev wrote:
> On Wed, Jun 04, 2014 at 08:18:42AM -0600, Jens Axboe wrote:
>> A null_blk test is the absolute best case for percpu_ida, since
>> there are enough tags and everything is localized. The above test is
>> more useful for testing blk-mq than any real world application of
>> the tagging.
>>
>> I've done considerable testing on both 2 and 4 socket (32 and 64
>> CPUs) and bitmap tagging is better in a much wider range of
>> applications. This includes even high tag depth devices like nvme,
>> and more normal ranges like mtip32xx and scsi-mq setups.
>
> Just for the record: bitmap tags on a 48 CPU box with NVMe device
> indeed shows almost the same performance/cache rate as the stock
> kernel.
Thanks for confirming. It's one of the dangers of null_blk, it's not
always a very accurate simulation of what a real device will do. I think
it's mostly a completion side thing, would be great with a small device
that supported msi-x and could be used as an irq trigger :-)
--
Jens Axboe
next prev parent reply other threads:[~2014-06-05 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 10:35 blk-mq: bitmap tag: performance degradation? Alexander Gordeev
2014-06-04 14:18 ` Jens Axboe
2014-06-05 14:01 ` Alexander Gordeev
2014-06-05 14:03 ` Jens Axboe [this message]
2014-06-05 14:16 ` Ming Lei
2014-06-05 17:17 ` Jens Axboe
2014-06-05 23:33 ` Ming Lei
2014-06-06 1:55 ` Jens Axboe
2014-06-06 2:03 ` Ming Lei
2014-06-06 2:35 ` Ming Lei
2014-06-06 2:40 ` 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=53907895.8090102@kernel.dk \
--to=axboe@kernel.dk \
--cc=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.