From: Oscar Salvador <osalvador@suse.de>
To: Peter Xu <peterx@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Breno Leitao <leitao@debian.org>, Rik van Riel <riel@surriel.com>,
Muchun Song <muchun.song@linux.dev>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Ackerley Tng <ackerleytng@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2 3/7] mm/hugetlb: Rename avoid_reserve to cow_from_owner
Date: Mon, 13 Jan 2025 12:20:34 +0100 [thread overview]
Message-ID: <Z4T3Ap7M-Jw2KJZ7@localhost.localdomain> (raw)
In-Reply-To: <20250107204002.2683356-4-peterx@redhat.com>
On Tue, Jan 07, 2025 at 03:39:58PM -0500, Peter Xu wrote:
> The old name "avoid_reserve" can be too generic and can be used wrongly in
> the new call sites that want to allocate a hugetlb folio.
>
> It's confusing on two things: (1) whether one can opt-in to avoid global
> reservation, and (2) whether it should take more than one count.
>
> In reality, this flag is only used in an extremely hacky path, in an
> extremely hacky way in hugetlb CoW path only, and always use with 1 saying
> "skip global reservation". Rename the flag to avoid future abuse of this
> flag, making it a boolean so as to reflect its true representation that
> it's not a counter. To make it even harder to abuse, add a comment above
> the function to explain it.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
I agree that the current name is quite misleading, and this patch
improves the situation substantially.
The only thing I am missing here is that the comment you added could be
more explanatory as to why new call sites do not want to make use of the
flag.
IIRC, not using so, will bypass all vma level reservations as you
mentioned, which means that the child can get killed if the parent
makes use of the page, as it is the parent the only one that made a
reservation.
So maybe dropping a hint would be nice.
Reviewed-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2025-01-13 11:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 20:39 [PATCH v2 0/7] mm/hugetlb: Refactor hugetlb allocation resv accounting Peter Xu
2025-01-07 20:39 ` [PATCH v2 1/7] mm/hugetlb: Fix avoid_reserve to allow taking folio from subpool Peter Xu
2025-01-13 11:02 ` Oscar Salvador
2025-01-07 20:39 ` [PATCH v2 2/7] mm/hugetlb: Stop using avoid_reserve flag in fork() Peter Xu
2025-01-13 11:05 ` Oscar Salvador
2025-01-07 20:39 ` [PATCH v2 3/7] mm/hugetlb: Rename avoid_reserve to cow_from_owner Peter Xu
2025-01-13 11:20 ` Oscar Salvador [this message]
2025-01-13 16:19 ` Peter Xu
2025-01-16 10:15 ` Oscar Salvador
2025-01-16 14:26 ` Peter Xu
2025-01-07 20:39 ` [PATCH v2 4/7] mm/hugetlb: Clean up map/global resv accounting when allocate Peter Xu
2025-01-13 22:57 ` Ackerley Tng
2025-01-14 18:25 ` Peter Xu
2025-01-07 20:40 ` [PATCH v2 5/7] mm/hugetlb: Simplify vma_has_reserves() Peter Xu
2025-01-07 20:40 ` [PATCH v2 6/7] mm/hugetlb: Drop vma_has_reserves() Peter Xu
2025-01-07 20:40 ` [PATCH v2 7/7] mm/hugetlb: Unify restore reserve accounting for new allocations Peter Xu
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=Z4T3Ap7M-Jw2KJZ7@localhost.localdomain \
--to=osalvador@suse.de \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--cc=roman.gushchin@linux.dev \
/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).