From: Vlastimil Babka <vbabka@suse.cz>
To: Shi Lei <shi_lei@massclouds.com>,
cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: remove useless lines in enable_cpucache()
Date: Thu, 30 Sep 2021 10:22:14 +0200 [thread overview]
Message-ID: <a6919b32-e789-7ed9-bab7-8235638e9c12@suse.cz> (raw)
In-Reply-To: <20210930034845.2539-1-shi_lei@massclouds.com>
On 9/30/21 05:48, Shi Lei wrote:
> These lines are useless, so remove them.
I would clarify that they are useless after commit 10befea91b61 ("mm:
memcg/slab: use a single set of kmem_caches for all allocations")
> Signed-off-by: Shi Lei <shi_lei@massclouds.com>
Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> mm/slab.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/mm/slab.c b/mm/slab.c
> index 4d826394ffcb..01775fe0e002 100644
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -3900,8 +3900,6 @@ static int enable_cpucache(struct kmem_cache *cachep, gfp_t gfp)
> if (err)
> goto end;
>
> - if (limit && shared && batchcount)
> - goto skip_setup;
> /*
> * The head array serves three purposes:
> * - create a LIFO ordering, i.e. return objects that are cache-warm
> @@ -3944,7 +3942,6 @@ static int enable_cpucache(struct kmem_cache *cachep, gfp_t gfp)
> limit = 32;
> #endif
> batchcount = (limit + 1) / 2;
> -skip_setup:
> err = do_tune_cpucache(cachep, limit, batchcount, shared, gfp);
> end:
> if (err)
>
next prev parent reply other threads:[~2021-09-30 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 3:48 Shi Lei
2021-09-30 8:22 ` Vlastimil Babka [this message]
2021-10-04 1:09 ` David Rientjes
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=a6919b32-e789-7ed9-bab7-8235638e9c12@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--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=shi_lei@massclouds.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox