From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, axboe@kernel.dk, kent.overstreet@gmail.com
Subject: Re: + fs-break-generic_file_buffered_read-up-into-multiple-functions.patch added to -mm tree
Date: Wed, 28 Oct 2020 15:22:35 -0700 [thread overview]
Message-ID: <20201028152235.125172e46ae70ba4d7094469@linux-foundation.org> (raw)
In-Reply-To: <20201027133551.GW20115@casper.infradead.org>
On Tue, 27 Oct 2020 13:35:51 +0000 Matthew Wilcox <willy@infradead.org> wrote:
> On Sun, Oct 25, 2020 at 03:08:17PM -0700, akpm@linux-foundation.org wrote:
> > The patch titled
> > Subject: mm/filemap/c: freak generic_file_buffered_read up into multiple functions
> > has been added to the -mm tree. Its filename is
> > fs-break-generic_file_buffered_read-up-into-multiple-functions.patch
>
> Can we back this out? It really makes the THP patchset unhappy. I think
> we can do something like this afterwards, but doing it this way round is
> ridiculously hard.
Two concerns:
: On my test box, 4k buffered random reads go from ~150k to ~250k iops,
: and the improvements to big sequential reads are even bigger.
That's a big improvement! We want that improvement. Throwing it away
on behalf of an as-yet-unmerged feature patchset hurts. Can we expect that
this improvement will be available post-that-patchset? And when?
(This improvment is rather hard to believe, really - more details on the
test environment would be useful. Can we expect that people will in
general see similar benefits or was there something special about the
testing?)
Secondly,
: This incorporates the fix for IOCB_WAITQ handling that Jens just
: posted as well
Is this (mysterious, unreferenced!) fix against v1 of Kent's patchset,
or is it against mainline? If it's against mainline then it's
presumably first priority. Can we please get that sent out in a
standalone form asap?
next prev parent reply other threads:[~2020-10-28 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201025220817.XxXVE%akpm@linux-foundation.org>
2020-10-27 13:35 ` Matthew Wilcox
2020-10-28 22:22 ` Andrew Morton [this message]
2020-10-28 22:26 ` Jens Axboe
2020-10-29 13:57 ` Jens Axboe
2020-10-29 14:57 ` Matthew Wilcox
2020-10-29 15:02 ` Jens Axboe
2020-10-29 15:03 ` Matthew Wilcox
2020-10-29 15:05 ` Jens Axboe
2020-10-29 15:17 ` Jens Axboe
2020-10-28 22:50 ` Matthew Wilcox
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=20201028152235.125172e46ae70ba4d7094469@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=kent.overstreet@gmail.com \
--cc=linux-mm@kvack.org \
--cc=willy@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