From: Andrew Morton <akpm@linux-foundation.org>
To: zippermonkey <zzippermonkey@outlook.com>
Cc: zhangpengpeng0808@gmail.com, bruzzhang@tencent.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
vernhao@tencent.com, willy@infradead.org, zigiwang@tencent.com
Subject: Re: [PATCH 0/10] mm: Fix various readahead quirks
Date: Thu, 27 Jun 2024 14:13:31 -0700 [thread overview]
Message-ID: <20240627141331.30bc97bef0d1acfe38f2880f@linux-foundation.org> (raw)
In-Reply-To: <SYBP282MB2224ADAC7D8A689BCC18F78AB9D72@SYBP282MB2224.AUSP282.PROD.OUTLOOK.COM>
On Thu, 27 Jun 2024 14:10:48 +0800 zippermonkey <zzippermonkey@outlook.com> wrote:
> Tested-by: Zhang Peng <bruzzhang@tencent.com>
Thanks. I added this to the changelogs and pasted your testing results
into the [0/N] description.
prev parent reply other threads:[~2024-06-27 21:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 10:18 [PATCH 0/10] mm: Fix various readahead quirks Jan Kara
2024-06-25 10:18 ` [PATCH 01/10] readahead: Make sure sync readahead reads needed page Jan Kara
2024-06-25 10:18 ` [PATCH 02/10] filemap: Fix page_cache_next_miss() when no hole found Jan Kara
2024-06-25 10:18 ` [PATCH 03/10] readahead: Properly shorten readahead when falling back to do_page_cache_ra() Jan Kara
2024-06-25 10:18 ` [PATCH 04/10] readahead: Drop pointless index from force_page_cache_ra() Jan Kara
2024-06-25 10:18 ` [PATCH 05/10] readahead: Drop index argument of page_cache_async_readahead() Jan Kara
2024-06-25 10:18 ` [PATCH 06/10] readahead: Drop dead code in page_cache_ra_order() Jan Kara
2024-06-25 10:18 ` [PATCH 07/10] readahead: Drop dead code in ondemand_readahead() Jan Kara
2024-06-25 10:18 ` [PATCH 08/10] readahead: Disentangle async and sync readahead Jan Kara
2024-06-25 10:18 ` [PATCH 09/10] readahead: Fold try_context_readahead() into its single caller Jan Kara
2024-06-25 10:19 ` [PATCH 10/10] readahead: Simplify gotos in page_cache_sync_ra() Jan Kara
2024-06-25 17:12 ` [PATCH 0/10] mm: Fix various readahead quirks Josef Bacik
2024-06-27 3:04 ` Zhang Peng
2024-06-27 6:10 ` zippermonkey
2024-06-27 21:13 ` Andrew Morton [this message]
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=20240627141331.30bc97bef0d1acfe38f2880f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bruzzhang@tencent.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vernhao@tencent.com \
--cc=willy@infradead.org \
--cc=zhangpengpeng0808@gmail.com \
--cc=zigiwang@tencent.com \
--cc=zzippermonkey@outlook.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;
as well as URLs for NNTP newsgroup(s).