From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
"Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
Nimrod Oren <noren@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <liam@infradead.org>,
Nico Pache <nico.pache@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>,
Lance Yang <lance.yang@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
Kiryl Shutsemau <kas@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <brendan.jackman@linux.dev>,
Hugh Dickins <hughd@google.com>, Nirmoy Das <nirmoyd@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mm: remove min_free_kbytes adjustment for THP
Date: Wed, 9 Sep 2026 12:18:03 +0100 [thread overview]
Message-ID: <aqFAOLrybtyo6dd1@gremlin> (raw)
In-Reply-To: <20260909113836.6cbe8d17@pumpkin>
On Wed, Sep 09, 2026 at 11:38:36AM +0100, David Laight wrote:
> On Wed, 9 Sep 2026 09:11:04 +0100
> "Lorenzo Stoakes (ARM)" <ljs@kernel.org> wrote:
>
> > On Tue, Sep 08, 2026 at 03:30:30PM -0400, Johannes Weiner wrote:
> > > On Tue, Sep 08, 2026 at 08:24:38AM -0400, Zi Yan wrote:
> > > > On Tue Sep 8, 2026 at 7:54 AM EDT, Vlastimil Babka (SUSE) wrote:
> > > > > Given neither of the patchset versions achieved universal acceptance, could
> > > > > we try just disabling all the automatic (re)calculations of min_free_kbytes
> > > > > the first moment the sysctl gets adjusted from userspace?
> > > >
> > > > Sounds good to me. Johannes, WDYT?
> > >
> > > +1 That sounds good to me as well.
> >
> > Me also! :>)
>
> You might want some method of restoring the default behaviour.
> Maybe setting to 0 can be used (if that is just silly).
I suppose the concern would be an embedded user for some reason enabling
CONFIG_TRANSPARENT_HUGEPAGE and then defaulting to THP ->madvise and getting the
bigger reserves before somehow disabling it after boot.
But I'm not sure if this is something we really need to worry about?
>
> David
>
> >
> > --
> > Cheers, Lorenzo
> >
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-09-09 11:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 19:01 Nimrod Oren
2026-09-01 19:12 ` Michal Hocko
2026-09-01 20:01 ` Zi Yan
2026-09-01 20:44 ` Johannes Weiner
2026-09-01 21:09 ` Zi Yan
2026-09-01 22:09 ` Johannes Weiner
2026-09-02 1:49 ` Zi Yan
2026-09-02 13:02 ` Lorenzo Stoakes (ARM)
2026-09-02 16:04 ` Johannes Weiner
2026-09-02 16:47 ` Usama Arif
2026-09-02 17:02 ` Zi Yan
2026-09-02 17:24 ` Usama Arif
2026-09-02 17:13 ` Lorenzo Stoakes (ARM)
2026-09-03 18:58 ` Zi Yan
2026-09-04 15:20 ` Johannes Weiner
2026-09-08 10:40 ` Barry Song
2026-09-02 12:07 ` Nirmoy Das
2026-09-02 13:46 ` Lorenzo Stoakes (ARM)
2026-09-02 16:23 ` Johannes Weiner
2026-09-02 17:00 ` Lorenzo Stoakes (ARM)
2026-09-02 18:37 ` Johannes Weiner
2026-09-03 15:46 ` Lorenzo Stoakes (ARM)
2026-09-04 15:43 ` Johannes Weiner
2026-09-04 16:46 ` Lorenzo Stoakes (ARM)
2026-09-03 12:52 ` Michal Hocko
2026-09-02 16:41 ` Usama Arif
2026-09-08 11:54 ` Vlastimil Babka (SUSE)
2026-09-08 12:24 ` Zi Yan
2026-09-08 19:30 ` Johannes Weiner
2026-09-09 8:11 ` Lorenzo Stoakes (ARM)
2026-09-09 10:38 ` David Laight
2026-09-09 11:18 ` Lorenzo Stoakes (ARM) [this message]
2026-09-09 12:27 ` David Laight
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=aqFAOLrybtyo6dd1@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=brendan.jackman@linux.dev \
--cc=david.laight.linux@gmail.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=dtatulea@nvidia.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=nico.pache@linux.dev \
--cc=nirmoyd@nvidia.com \
--cc=noren@nvidia.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--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®