From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,willy@infradead.org,guoxuenan@huawei.com,jack@suse.cz,akpm@linux-foundation.org
Subject: [folded-merged] readahead-avoid-multiple-marked-readahead-pages-v2.patch removed from -mm tree
Date: Thu, 25 Jan 2024 23:54:41 -0800 [thread overview]
Message-ID: <20240126075444.3E96CC433F1@smtp.kernel.org> (raw)
The quilt patch titled
Subject: readahead: Avoid multiple marked readahead pages
has been removed from the -mm tree. Its filename was
readahead-avoid-multiple-marked-readahead-pages-v2.patch
This patch was dropped because it was folded into readahead-avoid-multiple-marked-readahead-pages.patch
------------------------------------------------------
From: Jan Kara <jack@suse.cz>
Subject: readahead: Avoid multiple marked readahead pages
Date: Tue, 23 Jan 2024 16:32:54 +0100
fix one more place where mark rounding was done as well
Link: https://lkml.kernel.org/r/20240123153254.5206-1-jack@suse.cz
Fixes: b9ff43dd2743 ("mm/readahead: Fix readahead with large folios")
Signed-off-by: Jan Kara <jack@suse.cz>
Cc: Guo Xuenan <guoxuenan@huawei.com>
Cc: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/readahead.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/readahead.c~readahead-avoid-multiple-marked-readahead-pages-v2
+++ a/mm/readahead.c
@@ -575,7 +575,7 @@ static void ondemand_readahead(struct re
* It's the expected callback index, assume sequential access.
* Ramp up sizes, and push forward the readahead window.
*/
- expected = round_up(ra->start + ra->size - ra->async_size,
+ expected = round_down(ra->start + ra->size - ra->async_size,
1UL << order);
if (index == expected || index == (ra->start + ra->size)) {
ra->start += ra->size;
_
Patches currently in -mm which might be from jack@suse.cz are
readahead-avoid-multiple-marked-readahead-pages.patch
reply other threads:[~2024-01-26 7:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240126075444.3E96CC433F1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=guoxuenan@huawei.com \
--cc=jack@suse.cz \
--cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.