From: Andrew Morton <akpm@linux-foundation.org>
To: Ankur Arora <ankur.a.arora@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
david@kernel.org, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, mingo@redhat.com, mjguzik@gmail.com,
luto@kernel.org, peterz@infradead.org, tglx@linutronix.de,
willy@infradead.org, raghavendra.kt@amd.com, chleroy@kernel.org,
ioworker0@gmail.com, boris.ostrovsky@oracle.com,
konrad.wilk@oracle.com
Subject: Re: [PATCH v10 7/8] mm, folio_zero_user: support clearing page ranges
Date: Wed, 17 Dec 2025 10:54:26 -0800 [thread overview]
Message-ID: <20251217105426.5f03b5e8abd2e50faee9f49f@linux-foundation.org> (raw)
In-Reply-To: <87fr994hot.fsf@oracle.com>
On Wed, 17 Dec 2025 00:48:50 -0800 Ankur Arora <ankur.a.arora@oracle.com> wrote:
> > At 42GB/sec, 32MB will take less than a
> > millisecond, yes? I'm not aware of us really having any latency
> > targets in these preemption modes, but 1 millisecond sounds pretty
> > good.
>
> Agreed. The only complaint threshold I see is 100ms (default value of
> sysctl_resched_latency_warn_ms) which is pretty far from ~1ms.
>
> And having a threshold of 32MB might benefit other applications since
> we won't be discarding their cachelines in favour of filling up the
> cache with zeroes.
>
> I think the only problem cases might be slow uarchs and workloads where
> the memory bus is saturated which might dilate the preemption latency.
>
> And, even if the operation takes say ~20ms, that should still leave us
> with a reasonably large margin.
> (And, any latency senstive users are probably not running with
> preempt=none/voluntary.)
So I think you're saying that yes, we should increase the chunk size?
If so, what's the timing on that? It would be nice to do it in the
current -rc cycle for testing reasons and so the changelogs can be
updated to reflect the altered performance numbers.
next prev parent reply other threads:[~2025-12-17 18:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 20:49 [PATCH v10 0/8] mm: folio_zero_user: clear contiguous pages Ankur Arora
2025-12-15 20:49 ` [PATCH v10 1/8] treewide: provide a generic clear_user_page() variant Ankur Arora
2025-12-18 7:11 ` David Hildenbrand (Red Hat)
2025-12-18 19:31 ` Ankur Arora
2025-12-15 20:49 ` [PATCH v10 2/8] highmem: introduce clear_user_highpages() Ankur Arora
2025-12-15 20:49 ` [PATCH v10 3/8] mm: introduce clear_pages() and clear_user_pages() Ankur Arora
2025-12-15 20:49 ` [PATCH v10 4/8] highmem: do range clearing in clear_user_highpages() Ankur Arora
2025-12-18 7:15 ` David Hildenbrand (Red Hat)
2025-12-18 20:01 ` Ankur Arora
2025-12-15 20:49 ` [PATCH v10 5/8] x86/mm: Simplify clear_page_* Ankur Arora
2025-12-15 20:49 ` [PATCH v10 6/8] x86/clear_page: Introduce clear_pages() Ankur Arora
2025-12-18 7:22 ` David Hildenbrand (Red Hat)
2025-12-15 20:49 ` [PATCH v10 7/8] mm, folio_zero_user: support clearing page ranges Ankur Arora
2025-12-16 2:44 ` Andrew Morton
2025-12-16 6:49 ` Ankur Arora
2025-12-16 15:12 ` Andrew Morton
2025-12-17 8:48 ` Ankur Arora
2025-12-17 18:54 ` Andrew Morton [this message]
2025-12-17 19:51 ` Ankur Arora
2025-12-17 20:26 ` Andrew Morton
2025-12-18 0:51 ` Ankur Arora
2025-12-18 7:36 ` David Hildenbrand (Red Hat)
2025-12-18 20:16 ` Ankur Arora
2025-12-15 20:49 ` [PATCH v10 8/8] mm: folio_zero_user: cache neighbouring pages Ankur Arora
2025-12-18 7:49 ` David Hildenbrand (Red Hat)
2025-12-18 21:01 ` Ankur Arora
2025-12-18 21:23 ` Ankur Arora
2025-12-23 10:11 ` David Hildenbrand (Red Hat)
2025-12-16 2:48 ` [PATCH v10 0/8] mm: folio_zero_user: clear contiguous pages Andrew Morton
2025-12-16 5:04 ` Ankur Arora
2025-12-18 7:38 ` David Hildenbrand (Red Hat)
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=20251217105426.5f03b5e8abd2e50faee9f49f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ankur.a.arora@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=chleroy@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=ioworker0@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mjguzik@gmail.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=x86@kernel.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