From: Mike Snitzer <snitzer@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org,
linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: [LSF/MM TOPIC ATTEND] multipath for NVMe over Fabrics
Date: Thu, 8 Dec 2016 20:16:56 -0500 [thread overview]
Message-ID: <20161209011656.GA320@redhat.com> (raw)
I'd like to discuss $subject. I haven't heard of much progress on this
(but I'm also not tracking NVMe development at the moment).
Last I heard about getting DM multipath to work with NVMe over Fabrics
was this: https://patchwork.kernel.org/patch/9208997/
I've reintroduced bio-based support for the DM multipath target.
Between now and LSF I hope to come to terms with what the various work
items are for making DM multipath work for NVMeoF. I welcome any
ideas/thoughts others might have.
Mike
WARNING: multiple messages have this Message-ID (diff)
From: snitzer@redhat.com (Mike Snitzer)
Subject: [LSF/MM TOPIC ATTEND] multipath for NVMe over Fabrics
Date: Thu, 8 Dec 2016 20:16:56 -0500 [thread overview]
Message-ID: <20161209011656.GA320@redhat.com> (raw)
I'd like to discuss $subject. I haven't heard of much progress on this
(but I'm also not tracking NVMe development at the moment).
Last I heard about getting DM multipath to work with NVMe over Fabrics
was this: https://patchwork.kernel.org/patch/9208997/
I've reintroduced bio-based support for the DM multipath target.
Between now and LSF I hope to come to terms with what the various work
items are for making DM multipath work for NVMeoF. I welcome any
ideas/thoughts others might have.
Mike
next reply other threads:[~2016-12-09 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 1:16 Mike Snitzer [this message]
2016-12-09 1:16 ` [LSF/MM TOPIC ATTEND] multipath for NVMe over Fabrics Mike Snitzer
2016-12-09 6:43 ` Hannes Reinecke
2016-12-09 6:43 ` Hannes Reinecke
2016-12-09 6:43 ` Hannes Reinecke
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=20161209011656.GA320@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@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 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.