From: Matthew Wilcox <willy@infradead.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Kalesh Singh <kaleshsingh@google.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
lsf-pc@lists.linux-foundation.org,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
David Hildenbrand <david@redhat.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Juan Yescas <jyescas@google.com>,
android-mm <android-mm@google.com>,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Nhat Pham <nphamcs@gmail.com>
Subject: Re: [LSF/MM/BPF TOPIC] Optimizing Page Cache Readahead Behavior
Date: Sun, 23 Feb 2025 12:24:49 +0000 [thread overview]
Message-ID: <Z7sTkQAWt1X15wN0@casper.infradead.org> (raw)
In-Reply-To: <31e946de-b8d5-4681-b2ac-006360895a87@lucifer.local>
On Sun, Feb 23, 2025 at 09:30:57AM +0000, Lorenzo Stoakes wrote:
> It seems strange to me sparse regions would place duplicate zeroed pages in
> the page cache...
https://lore.kernel.org/linux-mm/Z7p-SLdiyQCknetc@casper.infradead.org/
next prev parent reply other threads:[~2025-02-23 12:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 21:13 [LSF/MM/BPF TOPIC] Optimizing Page Cache Readahead Behavior Kalesh Singh
2025-02-22 18:03 ` Kent Overstreet
2025-02-23 5:36 ` Kalesh Singh
2025-02-23 5:42 ` Kalesh Singh
2025-02-23 9:30 ` Lorenzo Stoakes
2025-02-23 12:24 ` Matthew Wilcox [this message]
2025-02-23 5:34 ` Ritesh Harjani
2025-02-23 6:50 ` Kalesh Singh
2025-02-24 12:56 ` David Sterba
2025-02-24 14:14 ` [Lsf-pc] " Jan Kara
2025-02-24 14:21 ` Lorenzo Stoakes
2025-02-24 16:31 ` Jan Kara
2025-02-24 16:52 ` Lorenzo Stoakes
2025-02-24 21:36 ` Kalesh Singh
2025-02-24 21:55 ` Kalesh Singh
2025-02-24 23:56 ` Dave Chinner
2025-02-25 6:45 ` Kalesh Singh
2025-02-27 22:12 ` Matthew Wilcox
2025-02-28 1:12 ` Dave Chinner
2025-02-28 9:07 ` David Hildenbrand
2025-04-02 0:13 ` Kalesh Singh
2025-02-25 5:44 ` Lorenzo Stoakes
2025-02-25 6:59 ` Kalesh Singh
2025-02-25 16:36 ` Jan Kara
2025-02-26 0:49 ` Kalesh Singh
2025-02-25 16:21 ` Jan Kara
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=Z7sTkQAWt1X15wN0@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=android-mm@google.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=jyescas@google.com \
--cc=kaleshsingh@google.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@suse.com \
--cc=nphamcs@gmail.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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).