From: "Li Zhe" <lizhe.67@bytedance.com>
To: <fvdl@google.com>
Cc: <akpm@linux-foundation.org>, <david@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<lizhe.67@bytedance.com>, <muchun.song@linux.dev>,
<osalvador@suse.de>
Subject: Re: [PATCH 0/8] Introduce a huge-page pre-zeroing mechanism
Date: Mon, 29 Dec 2025 20:28:56 +0800 [thread overview]
Message-ID: <20251229122856.7397-1-lizhe.67@bytedance.com> (raw)
In-Reply-To: <CAPTztWZroGx5AqB-2+EmSnqsCRtRjw5uvrNi_h7=JefZURB6Lw@mail.gmail.com>
On Fri, 26 Dec 2025 13:42:13 -0800, fvdl@google.com wrote:
> Is there any situation where you would write anything else than 'max'
> to the new sysfs file? E.g. in which scenarios does it make sense to
> *not* pre-zero all freed hugetlb folios? There doesn't seem to be a
> point to just doing a certain number. You can't know for sure if the
> number you read will remain correct, as it's just a snapshot. So how
> would you determine a correct number other than 'max'?
My view is that each application knows its own huge-page requirement
and should therefore write the corresponding number into the
"zeroable_hugepages" interface. Since the zeroing work is accounted
to the application process, the CPU time it consumes can be
constrained through that process's cgroup.
Thanks,
Zhe
next prev parent reply other threads:[~2025-12-29 12:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 8:20 李喆
2025-12-25 8:20 ` [PATCH 1/8] mm/hugetlb: add pre-zeroed framework 李喆
2025-12-26 9:24 ` Raghavendra K T
2025-12-26 9:48 ` Li Zhe
2025-12-25 8:20 ` [PATCH 2/8] mm/hugetlb: convert to prep_account_new_hugetlb_folio() 李喆
2025-12-25 8:20 ` [PATCH 3/8] mm/hugetlb: move the huge folio to the end of the list during enqueue 李喆
2025-12-25 8:20 ` [PATCH 4/8] mm/hugetlb: introduce per-node sysfs interface "zeroable_hugepages" 李喆
2025-12-26 18:51 ` Frank van der Linden
2025-12-29 12:25 ` Li Zhe
2025-12-29 18:57 ` Frank van der Linden
2025-12-30 2:41 ` Li Zhe
2025-12-25 8:20 ` [PATCH 5/8] mm/hugetlb: simplify function hugetlb_sysfs_add_hstate() 李喆
2025-12-25 8:20 ` [PATCH 6/8] mm/hugetlb: relocate the per-hstate struct kobject pointer 李喆
2025-12-25 8:20 ` [PATCH 7/8] mm/hugetlb: add epoll support for interface "zeroable_hugepages" 李喆
2025-12-25 8:20 ` [PATCH 8/8] mm/hugetlb: limit event generation frequency of function do_zero_free_notify() 李喆
2025-12-26 18:32 ` [PATCH 0/8] Introduce a huge-page pre-zeroing mechanism Frank van der Linden
2025-12-26 21:42 ` Frank van der Linden
2025-12-29 12:28 ` Li Zhe [this message]
2025-12-27 7:21 ` Mateusz Guzik
2025-12-29 12:31 ` Li Zhe
2025-12-28 21:44 ` Andrew Morton
2025-12-29 12:34 ` Li Zhe
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=20251229122856.7397-1-lizhe.67@bytedance.com \
--to=lizhe.67@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=fvdl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
/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