From: Hannes Reinecke <hare@suse.de>
To: Benjamin Marzinski <bmarzins@redhat.com>,
lsf-pc@lists.linux-foundation.org
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [LSF/MM ATTEND] multipath redesign and dm blk-mq issues
Date: Fri, 29 Jan 2016 07:59:09 +0100 [thread overview]
Message-ID: <56AB0DBD.6000605@suse.de> (raw)
In-Reply-To: <20160128212315.GX24960@octiron.msp.redhat.com>
On 01/28/2016 10:23 PM, Benjamin Marzinski wrote:
> 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.
>
And while you're there, we should be discussing systemd / udev
/dracut integration. I have sunk far too many man-hours into this,
and it's still nowhere near mainline.
And I guess the same goes for any other distro :-)
That doesn't warrant a full LSF session, though, the important bit
is the discussion itself :-)
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-01-29 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 21:23 [LSF/MM ATTEND] multipath redesign and dm blk-mq issues Benjamin Marzinski
2016-01-28 22:37 ` 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 [this message]
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=56AB0DBD.6000605@suse.de \
--to=hare@suse.de \
--cc=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).