From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 0/2] nvme-multipath: round-robin I/O policy
Date: Fri, 16 Nov 2018 09:26:59 +0100 [thread overview]
Message-ID: <20181116082659.GA14334@lst.de> (raw)
In-Reply-To: <20181115122927.40431-1-hare@suse.de>
On Thu, Nov 15, 2018@01:29:25PM +0100, Hannes Reinecke wrote:
> Hi all,
>
> after my NUMA path balancing patch hasn't met with universal approval,
Were there any good arguments against it vs just my implementation
nitpicks?
> here's now my take on a 'real' round-robin I/O scheduler for NVMe multipathing.
> With this patch I'm able to boost I/O performance from 127k/127k randrw
> to 156k/156k randrw (as measured by fio).
Either way that is some horribly bad performance. How much can
you get by driving one namespace on each path invididually?
next prev parent reply other threads:[~2018-11-16 8:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 12:29 [PATCH 0/2] nvme-multipath: round-robin I/O policy Hannes Reinecke
2018-11-15 12:29 ` [PATCH 1/2] nvme-multipath: add 'iopolicy' subsystem attribute Hannes Reinecke
2018-11-15 17:35 ` Sagi Grimberg
2018-11-16 8:07 ` Hannes Reinecke
2018-11-15 12:29 ` [PATCH 2/2] nvme-multipath: round-robin I/O policy Hannes Reinecke
2018-11-20 16:42 ` Christoph Hellwig
2018-11-20 20:30 ` Hannes Reinecke
2018-11-21 8:28 ` Christoph Hellwig
2018-11-21 11:24 ` Hannes Reinecke
[not found] ` <8a583536-151e-6f68-f4f9-98d8c4b853dd@broadcom.com>
2018-11-21 11:09 ` Hannes Reinecke
2018-11-22 13:52 ` Hannes Reinecke
2018-11-16 8:26 ` Christoph Hellwig [this message]
2018-11-20 16:02 ` [PATCH 0/2] " Hannes Reinecke
2018-11-20 16:19 ` Christoph Hellwig
2018-12-05 20:05 ` Ewan D. Milne
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=20181116082659.GA14334@lst.de \
--to=hch@lst.de \
/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).