From: Mike Snitzer <snitzer@redhat.com>
To: Ming Lin <mlin@kernel.org>
Cc: device-mapper development <dm-devel@redhat.com>,
linux-nvme@lists.infradead.org
Subject: Re: NVMeoF multi-path setup
Date: Thu, 30 Jun 2016 18:57:27 -0400 [thread overview]
Message-ID: <20160630225727.GC22293@redhat.com> (raw)
In-Reply-To: <20160630225207.GB22293@redhat.com>
On Thu, Jun 30 2016 at 6:52pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:
> Also, just so you're aware, I've staged bio-based dm-multipath support
> for the 4.8 merge window. Please see either the 'for-next' or 'dm-4.8'
> branch in linux-dm.git:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=for-next
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-4.8
>
> I'd welcome you testing if bio-based dm-multipath performs better for
> you than blk-mq request-based dm-multipath. Both modes (using the 4.8
> staged code) can be easily selected on a per DM multipath device table
> by adding either: queue_mode=bio or queue_mode=mq
>
> (made possible with this commit:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.8&id=e83068a5faafb8ca65d3b58bd1e1e3959ce1ddce
> )
Sorry, no = should be used. you need either:
"queue_mode bio" or "queue_mode mq"
Added to the features section of the "multipath" ctr input.
AFAIK, once the above commit lands upstream Ben will be adding some
multipath-tools code to make configuring queue_mode easy (but I think
multipath.conf may allow you to extend the features passed on a
per-device basis already.. but I'd have to look).
WARNING: multiple messages have this Message-ID (diff)
From: snitzer@redhat.com (Mike Snitzer)
Subject: NVMeoF multi-path setup
Date: Thu, 30 Jun 2016 18:57:27 -0400 [thread overview]
Message-ID: <20160630225727.GC22293@redhat.com> (raw)
In-Reply-To: <20160630225207.GB22293@redhat.com>
On Thu, Jun 30 2016 at 6:52pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:
> Also, just so you're aware, I've staged bio-based dm-multipath support
> for the 4.8 merge window. Please see either the 'for-next' or 'dm-4.8'
> branch in linux-dm.git:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=for-next
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-4.8
>
> I'd welcome you testing if bio-based dm-multipath performs better for
> you than blk-mq request-based dm-multipath. Both modes (using the 4.8
> staged code) can be easily selected on a per DM multipath device table
> by adding either: queue_mode=bio or queue_mode=mq
>
> (made possible with this commit:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.8&id=e83068a5faafb8ca65d3b58bd1e1e3959ce1ddce
> )
Sorry, no = should be used. you need either:
"queue_mode bio" or "queue_mode mq"
Added to the features section of the "multipath" ctr input.
AFAIK, once the above commit lands upstream Ben will be adding some
multipath-tools code to make configuring queue_mode easy (but I think
multipath.conf may allow you to extend the features passed on a
per-device basis already.. but I'd have to look).
next prev parent reply other threads:[~2016-06-30 22:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 21:08 NVMeoF multi-path setup Ming Lin
2016-06-30 21:08 ` Ming Lin
2016-06-30 21:57 ` Ming Lin
2016-06-30 21:57 ` Ming Lin
2016-06-30 22:19 ` Ming Lin
2016-06-30 22:19 ` Ming Lin
2016-06-30 22:52 ` Mike Snitzer
2016-06-30 22:52 ` Mike Snitzer
2016-06-30 22:57 ` Mike Snitzer [this message]
2016-06-30 22:57 ` Mike Snitzer
2016-06-30 23:14 ` Keith Busch
2016-06-30 23:14 ` Keith Busch
2016-07-13 10:19 ` Sagi Grimberg
2016-07-13 10:19 ` [dm-devel] " Sagi Grimberg
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=20160630225727.GC22293@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mlin@kernel.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.