From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: [LSF/MM ATTEND] multipath redesign and dm blk-mq issues
Date: Thu, 28 Jan 2016 15:23:15 -0600 [thread overview]
Message-ID: <20160128212315.GX24960@octiron.msp.redhat.com> (raw)
I'd like to attend LSF/MM 2016 to participate in any discussions about
redesigning how device-mapper multipath operates. I spend a significant
chunk of time dealing with issues around multipath and I'd like to
be part of any discussion about redesigning it.
In addition, I'd be interesting in disucssions that deal with how
device-mapper targets are dealing with blk-mq in general. For instance,
it looks like the current dm-multipath blk-mq implementation is running
into performance bottlenecks, and changing how path selection works into
something that allows for more parallelism is a worthy discussion. But
it would also be worth looking into changes about how the dm blk-mq
impementation deals with the mapping between it's swqueues and
hwqueue(s). Right now all the dm mapping is done in .queue_rq, instead
of in .map_queue, but I'm not convinced it belongs there. There's also
the issue that the bio targets may scale better on blk-mq devices than
the blk-mq targets.
If there happen to be any GFS2 related discussions, I'd be interested in
those as well.
Thanks
-Ben
next reply other threads:[~2016-01-28 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 21:23 Benjamin Marzinski [this message]
2016-01-28 22:37 ` [LSF/MM ATTEND] multipath redesign and dm blk-mq issues Mike Snitzer
2016-01-29 1:33 ` Benjamin Marzinski
2016-01-29 2:11 ` Benjamin Marzinski
2016-01-29 2:48 ` Mike Snitzer
2016-01-29 6:59 ` Hannes Reinecke
2016-01-29 15:34 ` Benjamin Marzinski
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=20160128212315.GX24960@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).