From: Mike Snitzer <snitzer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, dm-devel@redhat.com,
Alasdair Kergon <agk@redhat.com>,
stable@vger.kernel.org
Subject: Re: dm: give req_size precisely given by user
Date: Tue, 18 Dec 2018 14:47:09 -0500 [thread overview]
Message-ID: <20181218194708.GA24676@redhat.com> (raw)
In-Reply-To: <01a60138-63ab-6a9d-c0ba-b8fea551b14e@kernel.dk>
On Tue, Dec 18 2018 at 12:45pm -0500,
Jens Axboe <axboe@kernel.dk> wrote:
> On 12/18/18 10:25 AM, Jaegeuk Kim wrote:
> > This patch makes dm be aware of io_pages to assign sane req_size for reads.
>
> Reviewed-by: Jens Axboe <axboe@kernel.dk>
>
I've applied this, see:
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.21&id=c6d6e9b0f6b4201c77f2cea3964dd122697e3543
next prev parent reply other threads:[~2018-12-18 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 17:25 [PATCH] dm: give req_size precisely given by user Jaegeuk Kim
2018-12-18 17:45 ` Jens Axboe
2018-12-18 19:47 ` Mike Snitzer [this message]
2018-12-18 21:40 ` Jaegeuk Kim
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=20181218194708.GA24676@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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 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).