From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>, Ewan Milne <emilne@redhat.com>,
Uday Shankar <ushankar@purestorage.com>,
Randy Jennings <randyj@purestorage.com>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH RFC 0/2] nvme-multipath: additional iopolicies
Date: Wed, 26 Jul 2023 15:25:44 +0200 [thread overview]
Message-ID: <20230726132544.GA16873@lst.de> (raw)
In-Reply-To: <20230726132305.33739-1-hare@suse.de>
On Wed, Jul 26, 2023 at 03:23:03PM +0200, Hannes Reinecke wrote:
> Hi all,
>
> as Ewan raised the issue that we are suffering from a buffer-bloat
> problem when using the round-robin I/O scheduler here are additiona
> I/O schedulers to improve the situation.
> The schedulers are untested, and are compile-tested only.
> I just putting them out here as I had several requests for them;
> I'm happily improving them upon feedback.
FYI, the policy for nvme-multpath has mostly been that we want to
see very solid used cases. So in addition to actually testing
the code, I'd like to see detailed and solid use cases. And preferably
just one new policy and not three if possible..
next prev parent reply other threads:[~2023-07-26 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 13:23 [PATCH RFC 0/2] nvme-multipath: additional iopolicies Hannes Reinecke
2023-07-26 13:23 ` [PATCH 1/2] nvme-multipath: add " Hannes Reinecke
2023-07-26 13:23 ` [PATCH 2/2] nvme-multipath: add 'latency' iopolicy Hannes Reinecke
2023-07-26 13:25 ` Christoph Hellwig [this message]
2023-07-26 13:32 ` [PATCH RFC 0/2] nvme-multipath: additional iopolicies 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=20230726132544.GA16873@lst.de \
--to=hch@lst.de \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=randyj@purestorage.com \
--cc=sagi@grimberg.me \
--cc=ushankar@purestorage.com \
/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