From: sxwjean@me.com
To: cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, vbabka@suse.cz, roman.gushchin@linux.dev,
42.hyeyoo@gmail.com
Cc: corbet@lwn.net, linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] supplement of slab removal
Date: Mon, 20 Nov 2023 17:12:10 +0800 [thread overview]
Message-ID: <20231120091214.150502-1-sxwjean@me.com> (raw)
From: Xiongwei Song <xiongwei.song@windriver.com>
Hi,
These patches are based on [1] and repo [2], so they are supplement of slab
removal. There is no functionality changed.
[1] https://lore.kernel.org/linux-mm/20231113191340.17482-22-vbabka@suse.cz/T/#t
[2] https://git.kernel.org/pub/scm/linux/kernel/git/vbabka/linux.git/log/?h=slab-remove-slab-v1r4
Xiongwei Song (4):
Documentation: kernel-parameters: remove slab_max_order
mm/slab: remove slab_nomrege and slab_merge
mm/slab: make calculate_alignment() public
mm/slab: move slab merge from slab_common.c to slub.c
.../admin-guide/kernel-parameters.txt | 17 +--
mm/Kconfig | 2 +-
mm/slab.h | 5 +-
mm/slab_common.c | 103 +-----------------
mm/slub.c | 100 ++++++++++++++++-
5 files changed, 105 insertions(+), 122 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-20 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 9:12 sxwjean [this message]
2023-11-20 9:12 ` [PATCH 1/4] Documentation: kernel-parameters: remove slab_max_order sxwjean
2023-11-21 8:30 ` Hyeonggon Yoo
2023-11-22 5:19 ` Song, Xiongwei
2023-11-20 9:12 ` [PATCH 2/4] mm/slab: remove slab_nomrege and slab_merge sxwjean
2023-11-21 8:44 ` Hyeonggon Yoo
2023-11-22 5:27 ` Song, Xiongwei
2023-11-22 5:59 ` Hyeonggon Yoo
2023-11-20 9:12 ` [PATCH 3/4] mm/slab: make calculate_alignment() public sxwjean
2023-11-20 9:12 ` [PATCH 4/4] mm/slab: move slab merge from slab_common.c to slub.c sxwjean
2023-11-21 8:54 ` Hyeonggon Yoo
2023-11-21 10:03 ` Vlastimil Babka
2023-11-22 5:29 ` Song, Xiongwei
2023-11-21 9:01 ` Hyeonggon Yoo
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=20231120091214.150502-1-sxwjean@me.com \
--to=sxwjean@me.com \
--cc=42.hyeyoo@gmail.com \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/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