From: Bharata B Rao <bharata@amd.com>
To: Vinay Banakar <vny@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, willy@infradead.org, mgorman@suse.de,
Wei Xu <weixugc@google.com>, Greg Thelen <gthelen@google.com>
Subject: Re: [PATCH] mm: Optimize TLB flushes during page reclaim
Date: Wed, 22 Jan 2025 17:01:49 +0530 [thread overview]
Message-ID: <96e992ac-2213-46f6-ad82-e84dd07ce892@amd.com> (raw)
In-Reply-To: <CALf+9YdnpxRfLKqH4_u5XVLc_4d1H1f0b2gRx4-oAFL5NhQwvA@mail.gmail.com>
On 22-Jan-25 4:39 PM, Vinay Banakar wrote:
> On Wed, Jan 22, 2025 at 2:59 AM Bharata B Rao <bharata@amd.com> wrote:
>> and one flush request is issued for the entire list. Where is the PMD
>> level (512) batching done? Is that implicit elsewhere in the flow?
>
> Yes, shrink_folio_list() operates on one PMD at a time, so
> pageout_list will contain at most 512 pages during each call. Please
> refer to madvise_cold_or_pageout_pte_range() in mm/madvise.c for more
> details.
While that may be true for MADV_PAGEOUT path, does the same assumption
hold good for other paths from which shrink_folio_list() gets called?
Regards,
Bharata.
next prev parent reply other threads:[~2025-01-22 11:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 22:47 Vinay Banakar
2025-01-21 0:05 ` Vinay Banakar
2025-01-22 8:59 ` Bharata B Rao
2025-01-22 11:09 ` Vinay Banakar
2025-01-22 11:31 ` Bharata B Rao [this message]
2025-01-22 13:28 ` Vinay Banakar
2025-01-22 20:05 ` SeongJae Park
2025-01-23 17:11 ` Vinay Banakar
2025-01-23 17:23 ` SeongJae Park
2025-01-23 18:17 ` Matthew Wilcox
2025-01-21 1:43 ` Byungchul Park
2025-01-21 18:03 ` Vinay Banakar
2025-01-23 4:17 ` Rik van Riel
2025-01-23 19:16 ` Vinay Banakar
2025-01-28 22:01 ` Rik van Riel
2025-03-17 19:20 ` Rik van Riel
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=96e992ac-2213-46f6-ad82-e84dd07ce892@amd.com \
--to=bharata@amd.com \
--cc=akpm@linux-foundation.org \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=vny@google.com \
--cc=weixugc@google.com \
--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