From: Mike Snitzer <snitzer@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Junichi Nomura <j-nomura@ce.jp.nec.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-multipath performance patches
Date: Tue, 8 Mar 2016 09:48:42 -0500 [thread overview]
Message-ID: <20160308144842.GA13283@redhat.com> (raw)
In-Reply-To: <56DE81B5.80001@suse.de>
On Tue, Mar 08 2016 at 2:39am -0500,
Hannes Reinecke <hare@suse.de> wrote:
> Hi Mike,
>
> to picking up an old topic, what's the status of your performance
> patches for dm-multipath?
>
> I've started looking a branch 'devel3', and was wondering if these
> are the latest patches available.
> Or would you have newer?
The 'devel3' was just a temporary branch I was using during
development. I've since staged all the changes in linux-next via
linux-dm.git's 'for-next' branch:
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=for-next
If you could test this 'for-next' and report back I'd appreciate it.
It'd build my confidence in pushing these changes once the 4.6 merge
window opens.
That said, these changes have held up to Junichi's test suite. WHich
I've now staged here (until I get around to porting them over to
device-mapper-test-suite): https://github.com/snitm/mptest
As for code review, please have a good look at this commit:
b3c39bf1d dm mpath: convert from spinlock to RCU for most locking
If you find anything feel free to share an incremental fix and I'll get
it reviewed/staged.
(Junichi I'd welcome your review of all these request-based DM core and
multipath changes too)
Thanks,
Mike
next prev parent reply other threads:[~2016-03-08 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 7:39 dm-multipath performance patches Hannes Reinecke
2016-03-08 14:48 ` Mike Snitzer [this message]
2016-03-08 15:27 ` Hannes Reinecke
2016-03-08 17:40 ` Mike Snitzer
2016-03-12 13:45 ` Mike Snitzer
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=20160308144842.GA13283@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=j-nomura@ce.jp.nec.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).