From: David Hildenbrand <david@redhat.com>
To: Usama Arif <usamaarif642@gmail.com>, alx@kernel.org
Cc: linux-man@vger.kernel.org, lorenzo.stoakes@oracle.com,
hannes@cmpxchg.org, baohua@kernel.org, shakeel.butt@linux.dev,
ziy@nvidia.com, laoar.shao@gmail.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] PR_*ET_THP_DISABLE.2const: document addition of PR_THP_DISABLE_EXCEPT_ADVISED
Date: Mon, 1 Sep 2025 18:38:15 +0200 [thread overview]
Message-ID: <5af4b427-c07d-46d5-91a5-3b4616ef01ea@redhat.com> (raw)
In-Reply-To: <d45bfc2d-91da-4a70-90d2-4e0319c5241c@gmail.com>
On 01.09.25 18:18, Usama Arif wrote:
>
>
> On 01/09/2025 17:09, Usama Arif wrote:
>> PR_THP_DISABLE_EXCEPT_ADVISED extended PR_SET_THP_DISABLE to only provide
>> THPs when advised. IOW, it allows individual processes to opt-out of THP =
>> "always" into THP = "madvise", without affecting other workloads on the
>> system. The series has been merged in [1].
>>
>> This patch documents the changes introduced due to the addition of
>> PR_THP_DISABLE_EXCEPT_ADVISED flag:
>> - PR_GET_THP_DISABLE returns a value whose bits indicate how THP-disable
>> is configured for the calling thread (with or without
>> PR_THP_DISABLE_EXCEPT_ADVISED).
>> - PR_SET_THP_DISABLE now uses arg3 to specify whether to disable THP
>> completely for the process, or disable except madvise
>> (PR_THP_DISABLE_EXCEPT_ADVISED).
>>
>> [1] https://lore.kernel.org/all/20250815135549.130506-1-usamaarif642@gmail.com/
>>
>> Signed-off-by: Usama Arif <usamaarif642@gmail.com>
>> ---
>> man/man2/madvise.2 | 4 +-
>> man/man2const/PR_GET_THP_DISABLE.2const | 18 ++++++---
>> man/man2const/PR_SET_THP_DISABLE.2const | 52 +++++++++++++++++++++----
>> 3 files changed, 61 insertions(+), 13 deletions(-)
>>
>
> I am not sure what the right time is to send the mandoc changes.
> The patches have been merged into mm-new for more than 2 weeks.
> We can still review it and I can resend if needed after the kernel release if that
> is a more appropriate time?
Probably good to revive once it's in Linus' tree.
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-09-01 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 16:09 Usama Arif
2025-09-01 16:18 ` Usama Arif
2025-09-01 16:38 ` David Hildenbrand [this message]
2025-09-01 16:40 ` Alejandro Colomar
2025-09-01 17:01 ` Usama Arif
2025-09-01 16:36 ` Alejandro Colomar
2025-09-01 16:58 ` Usama Arif
2025-09-02 8:19 ` Alejandro Colomar
2025-09-05 13:25 Usama Arif
2025-09-05 13:26 ` Usama Arif
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=5af4b427-c07d-46d5-91a5-3b4616ef01ea@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=alx@kernel.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=shakeel.butt@linux.dev \
--cc=usamaarif642@gmail.com \
--cc=ziy@nvidia.com \
/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
all inboxes | Powered by JetHome®