From: "Christoph Lameter (Ampere)" <cl@linux.com>
To: "Song, Xiongwei" <Xiongwei.Song@windriver.com>
Cc: Chengming Zhou <chengming.zhou@linux.dev>,
Vlastimil Babka <vbabka@suse.cz>,
Yosry Ahmed <yosryahmed@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
David Rientjes <rientjes@google.com>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Chengming Zhou <zhouchengming@bytedance.com>,
Zheng Yejian <zhengyejian1@huawei.com>
Subject: RE: Do we still need SLAB_MEM_SPREAD (and possibly others)?
Date: Mon, 5 Feb 2024 09:50:15 -0800 (PST) [thread overview]
Message-ID: <fb8161d9-16c0-da8c-09ee-905e39ae199b@linux.com> (raw)
In-Reply-To: <PH0PR11MB519280092AA66FAE6BB3FACEEC402@PH0PR11MB5192.namprd11.prod.outlook.com>
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.
next prev parent reply other threads:[~2024-02-05 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 22:20 Do we still need SLAB_MEM_SPREAD (and possibly others)? Steven Rostedt
2024-01-31 22:25 ` Yosry Ahmed
2024-01-31 22:40 ` Vlastimil Babka
2024-02-01 6:27 ` Chengming Zhou
2024-02-04 2:06 ` Song, Xiongwei
2024-02-05 17:50 ` Christoph Lameter (Ampere) [this message]
2024-02-06 1:46 ` Song, Xiongwei
2024-02-06 3:16 ` Waiman Long
2024-02-06 3:20 ` Waiman Long
2024-02-06 3:25 ` Chengming Zhou
2024-02-06 3:34 ` Waiman Long
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=fb8161d9-16c0-da8c-09ee-905e39ae199b@linux.com \
--to=cl@linux.com \
--cc=42.hyeyoo@gmail.com \
--cc=Xiongwei.Song@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=yosryahmed@google.com \
--cc=zhengyejian1@huawei.com \
--cc=zhouchengming@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.