[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250731184533.16419-1-sj@kernel.org>
Date: Thu, 31 Jul 2025 11:45:33 -0700
From: SeongJae Park <sj@...nel.org>
To: "Huang, Ying" <ying.huang@...ux.alibaba.com>
Cc: SeongJae Park <sj@...nel.org>,
Joshua Hahn <joshua.hahnjy@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>,
Johannes Weiner <hannes@...xchg.org>,
Zi Yan <ziy@...dia.com>,
Matthew Brost <matthew.brost@...el.com>,
Rakie Kim <rakie.kim@...com>,
Byungchul Park <byungchul@...com>,
Gregory Price <gourry@...rry.net>,
Alistair Popple <apopple@...dia.com>,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org,
kernel-team@...a.com,
Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH] mempolicy: Clarify what RECLAIM_ZONE means
On Thu, 31 Jul 2025 09:48:54 +0800 "Huang, Ying" <ying.huang@...ux.alibaba.com> wrote:
> Joshua Hahn <joshua.hahnjy@...il.com> writes:
[...]
> > On that note, one thing that I felt was slightly undercaptured in
> > Documentation/admin-guide is what "zone reclaim" actually means. What it does
> > is of course well captured by its name, but it misses the nuance of preferring
> > reclaim over fallback allocation.
> >
> > Actually the whole motivation behind all of this conversation is because I saw
> > zone reclaim preventing allocation into a second node in a 2-NUMA node system
> > and was a bit confused until I understood what the implication of having
> > zone reclaim was.
>
> Yes. It's good to improve the document. If it makes you confusing, it
> may make others confusing too.
+1
Thanks,
SJ
[...]
Powered by blists - more mailing lists