From: Christoph Hellwig <hch@lst.de>
To: Baegjae Sung <baegjae@gmail.com>
Cc: keith.busch@intel.com, axboe@fb.com, hch@lst.de,
sagi@grimberg.me, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme-multipath: implement active-active round-robin path selector
Date: Wed, 28 Mar 2018 10:06:46 +0200 [thread overview]
Message-ID: <20180328080646.GB20373@lst.de> (raw)
In-Reply-To: <20180327043851.6640-1-baegjae@gmail.com>
For PCIe devices the right policy is not a round robin but to use
the pcie device closer to the node. I did a prototype for that
long ago and the concept can work. Can you look into that and
also make that policy used automatically for PCIe devices?
next prev parent reply other threads:[~2018-03-28 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 4:38 [PATCH] nvme-multipath: implement active-active round-robin path selector Baegjae Sung
2018-03-28 8:06 ` Christoph Hellwig [this message]
2018-03-28 19:47 ` Keith Busch
2018-03-29 8:56 ` Christoph Hellwig
2018-03-30 4:57 ` Baegjae Sung
2018-03-30 7:06 ` Christoph Hellwig
[not found] ` <e22676055aca4e8d936b7479d6301d85@skt-tnetpmx2.SKT.AD>
2018-04-04 14:30 ` Keith Busch
2018-04-04 12:36 ` Sagi Grimberg
2018-04-04 12:39 ` 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=20180328080646.GB20373@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=baegjae@gmail.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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