From: Vlastimil Babka <vbabka@suse.cz>
To: Chengming Zhou <chengming.zhou@linux.dev>
Cc: akpm@linux-foundation.org, cl@linux.com, penberg@kernel.org,
rientjes@google.com, iamjoonsoo.kim@lge.com,
roman.gushchin@linux.dev, 42.hyeyoo@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: remove PARTIAL_NODE slab_state
Date: Tue, 5 Mar 2024 11:14:32 +0100 [thread overview]
Message-ID: <80269a92-1242-49be-97c5-315c0621a1d3@suse.cz> (raw)
In-Reply-To: <20240305083913.1494784-1-chengming.zhou@linux.dev>
On 3/5/24 09:39, Chengming Zhou wrote:
> The PARTIAL_NODE slab_state has gone with SLAB removed, so just
> remove it.
>
> Signed-off-by: Chengming Zhou <chengming.zhou@linux.dev>
Thanks, queued.
> ---
> mm/slab.h | 1 -
> tools/include/linux/slab.h | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/mm/slab.h b/mm/slab.h
> index 96cb74be4b69..d2bc9b191222 100644
> --- a/mm/slab.h
> +++ b/mm/slab.h
> @@ -363,7 +363,6 @@ static inline int objs_per_slab(const struct kmem_cache *cache,
> enum slab_state {
> DOWN, /* No slab functionality yet */
> PARTIAL, /* SLUB: kmem_cache_node available */
> - PARTIAL_NODE, /* SLAB: kmalloc size for node struct available */
> UP, /* Slab caches usable but not all extras yet */
> FULL /* Everything is working */
> };
> diff --git a/tools/include/linux/slab.h b/tools/include/linux/slab.h
> index 311759ea25e9..51b25e9c4ec7 100644
> --- a/tools/include/linux/slab.h
> +++ b/tools/include/linux/slab.h
> @@ -18,7 +18,6 @@ bool slab_is_available(void);
> enum slab_state {
> DOWN,
> PARTIAL,
> - PARTIAL_NODE,
> UP,
> FULL
> };
prev parent reply other threads:[~2024-03-05 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 8:39 Chengming Zhou
2024-03-05 10:14 ` Vlastimil Babka [this message]
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=80269a92-1242-49be-97c5-315c0621a1d3@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
/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