From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <keith.busch@intel.com>,
Linux Block <linux-block@vger.kernel.org>,
Linux NVMe <linux-nvme@lists.infradead.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCHv2 2/2] block: Handle merging discards in IO schedulers
Date: Thu, 1 Feb 2018 14:02:14 -0700 [thread overview]
Message-ID: <d2b2eb11-fb1c-91a9-604b-d2dddac88a45@kernel.dk> (raw)
In-Reply-To: <20180201203158.24761-3-keith.busch@intel.com>
On 2/1/18 1:31 PM, Keith Busch wrote:
> This adds support for merging discard requests in all IO schedulers.
As per my last email, some of these aren't correct. Only the
blk-mq-sched change is correct/useful, so we should just do that
separately.
--
Jens Axboe
next prev parent reply other threads:[~2018-02-01 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 20:31 [PATCHv2 0/2] block: Discard merging fixes Keith Busch
2018-02-01 20:31 ` [PATCHv2 1/2] block: Merge discard requests as a special case Keith Busch
2018-02-01 21:00 ` Jens Axboe
2018-02-01 20:31 ` [PATCHv2 2/2] block: Handle merging discards in IO schedulers Keith Busch
2018-02-01 21:02 ` Jens Axboe [this message]
2018-02-01 21:28 ` Keith Busch
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=d2b2eb11-fb1c-91a9-604b-d2dddac88a45@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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 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).