From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: <cl@linux.com>, <penberg@kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH] mm/slab.c: Update outdated kmem_list3 in a comment
Date: Thu, 30 Jul 2020 21:31:37 +0800 [thread overview]
Message-ID: <5F22CBB9.1080905@cn.fujitsu.com> (raw)
In-Reply-To: <20200722033355.26908-1-yangx.jy@cn.fujitsu.com>
Hi,
Ping.
On 2020/7/22 11:33, Xiao Yang wrote:
> kmem_list3 has been renamed to kmem_cache_node long long
> ago so update it.
>
> References:
> '6744f087ba2a ("slab: Common name for the per node structures")'
> 'ce8eb6c424c7 ("slab: Rename list3/l3 to node")'
>
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
> ---
> mm/slab.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/slab.c b/mm/slab.c
> index 9350062ffc1a..a7988aeb9bc3 100644
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -1050,7 +1050,7 @@ int slab_prepare_cpu(unsigned int cpu)
> * offline.
> *
> * Even if all the cpus of a node are down, we don't free the
> - * kmem_list3 of any cache. This to avoid a race between cpu_down, and
> + * kmem_cache_node of any cache. This to avoid a race between cpu_down, and
> * a kmalloc allocation from another cpu for memory from the node of
> * the cpu going down. The list3 structure is usually allocated from
> * kmem_cache_create() and gets destroyed at kmem_cache_destroy().
next prev parent reply other threads:[~2020-07-30 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 3:33 [PATCH] mm/slab.c: Update outdated kmem_list3 in a comment Xiao Yang
2020-07-30 13:31 ` Xiao Yang [this message]
2020-07-30 16:36 ` Pekka Enberg
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=5F22CBB9.1080905@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=cl@linux.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).