From: Johannes Thumshirn <jthumshirn@suse.de>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, linux-scsi@vger.kernel.org,
sagig@dev.mellanox.co.il, linux-block@vger.kernel.org,
jmoyer@redhat.com, j-nomura@ce.jp.nec.com, hare@suse.de
Subject: Re: [RFC PATCH 0/4] dm mpath: vastly improve blk-mq IO performance
Date: Fri, 01 Apr 2016 15:37:36 +0200 [thread overview]
Message-ID: <cddb09e2c2af7f7ea0337cf76657c896@suse.de> (raw)
In-Reply-To: <20160401132219.GA24355@redhat.com>
[ +Cc Hannes ]
On 2016-04-01 15:22, Mike Snitzer wrote:
> On Fri, Apr 01 2016 at 4:12am -0400,
> Johannes Thumshirn <jthumshirn@suse.de> wrote:
>
>> On 2016-03-31 22:04, Mike Snitzer wrote:
>> >I developed these changes some weeks ago but have since focused on
>> >regression and performance testing on larger NUMA systems.
>> >
>> >For regression testing I've been using mptest:
>> >https://github.com/snitm/mptest
>> >
>> >For performance testing I've been using a null_blk device (with
>> >various configuration permutations, e.g. pinning memory to a
>> >particular NUMA node, and varied number of submit_queues).
>> >
>> >By eliminating multipath's heavy use of the m->lock spinlock in the
>> >fast IO paths serious performance improvements are realized.
>>
>> Hi Mike,
>>
>> Are this the patches you pointed Hannes to?
>>
>> If yes, please add my Tested-by: Johannes Thumshirn
>> <jthumshirn@suse.de>
>
> No they are not.
>
> Hannes seems to have last pulled in my DM mpath changes that (ab)used
> RCU.
> I ended up dropping those changes and this patchset is the replacement.
Now that you're saying it I can remember some inspiring RCU usage in the
patches.
> So please retest with this patchset (I know you guys have a large setup
> that these changes are very relevant for). If you could actually share
> _how_ yo've tested that'd help me understand how these changes are
> holding up. So far all looks good for me...
The test itself is actually quite simple, we're testing with fio against
a fiber channel array (all SSDs but I was very careful to only write
into the cache)
Here's my fio job file:
[mq-test]
iodepth=128
numjobs=40
group_reporting
direct=1
ioengine=libaio
size=3G
filename=/dev/dm-0
filename=/dev/dm-1
filename=/dev/dm-2
filename=/dev/dm-3
filename=/dev/dm-4
filename=/dev/dm-5
filename=/dev/dm-6
filename=/dev/dm-7
name="MQ Test"
and the test runner:
#!/bin/sh
for rw in 'randread' 'randwrite' 'read' 'write'; do
for bs in '4k' '8k' '16k' '32k' '64k'; do
fio mq-test.fio --bs="${bs}" --rw="${rw}"
--output="fio-${bs}-${rw}.txt"
done
done
The initiator has 40 CPUs on 4 NUMA nodes (no HT) and 64GB RAM. I'm not
sure how much in term of numbers I can share from the old patchset (will
ask Hannes on Monday), but I'm aware I'll have to when I retested with
your new patches and we want to compare the results.
Byte,
Johannes
next prev parent reply other threads:[~2016-04-01 13:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 20:04 [RFC PATCH 0/4] dm mpath: vastly improve blk-mq IO performance Mike Snitzer
2016-03-31 20:04 ` [RFC PATCH 1/4] dm mpath: switch to using bitops for state flags Mike Snitzer
2016-04-01 8:46 ` [dm-devel] " Johannes Thumshirn
2016-04-07 14:59 ` Hannes Reinecke
2016-03-31 20:04 ` [RFC PATCH 2/4] dm mpath: use atomic_t for counting members of 'struct multipath' Mike Snitzer
2016-04-01 8:48 ` [dm-devel] " Johannes Thumshirn
2016-04-07 15:02 ` Hannes Reinecke
2016-03-31 20:04 ` [RFC PATCH 3/4] dm mpath: move trigger_event member to the end " Mike Snitzer
2016-04-01 8:50 ` [dm-devel] " Johannes Thumshirn
2016-04-07 15:03 ` Hannes Reinecke
2016-03-31 20:04 ` [RFC PATCH 4/4] dm mpath: eliminate use of spinlock in IO fast-paths Mike Snitzer
2016-04-01 9:02 ` [dm-devel] " Johannes Thumshirn
2016-04-07 15:03 ` Hannes Reinecke
2016-04-01 8:12 ` [dm-devel] [RFC PATCH 0/4] dm mpath: vastly improve blk-mq IO performance Johannes Thumshirn
2016-04-01 13:22 ` Mike Snitzer
2016-04-01 13:37 ` Johannes Thumshirn [this message]
2016-04-01 14:14 ` Mike Snitzer
2016-04-07 14:58 ` Hannes Reinecke
2016-04-07 15:34 ` Mike Snitzer
2016-04-08 11:42 ` [dm-devel] " Johannes Thumshirn
2016-04-08 19:29 ` Mike Snitzer
2016-04-13 7:03 ` [dm-devel] " Johannes Thumshirn
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=cddb09e2c2af7f7ea0337cf76657c896@suse.de \
--to=jthumshirn@suse.de \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=j-nomura@ce.jp.nec.com \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sagig@dev.mellanox.co.il \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).