[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb8161d9-16c0-da8c-09ee-905e39ae199b@linux.com>
Date: Mon, 5 Feb 2024 09:50:15 -0800 (PST)
From: "Christoph Lameter (Ampere)" <cl@...ux.com>
To: "Song, Xiongwei" <Xiongwei.Song@...driver.com>
cc: Chengming Zhou <chengming.zhou@...ux.dev>,
Vlastimil Babka <vbabka@...e.cz>, Yosry Ahmed <yosryahmed@...gle.com>,
Steven Rostedt <rostedt@...dmis.org>, LKML <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>, David Rientjes <rientjes@...gle.com>,
Hyeonggon Yoo <42.hyeyoo@...il.com>,
Chengming Zhou <zhouchengming@...edance.com>,
Zheng Yejian <zhengyejian1@...wei.com>
Subject: RE: Do we still need SLAB_MEM_SPREAD (and possibly others)?
On Sun, 4 Feb 2024, Song, Xiongwei wrote:
> Once SLAB_MEM_SPREAD is removed, IMO, cpuset.memory_spread_slab is useless.
SLAB_MEM_SPREAD does not do anything anymore. SLUB relies on the
"spreading" via the page allocator memory policies instead of doing its
own like SLAB used to do.
What does FILE_SPREAD_SLAB do? Dont see anything there either.
Powered by blists - more mailing lists