From: Xiongwei Song <sxwjean@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Xiongwei Song <sxwjean@me.com>, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
longman@redhat.com, guro@fb.com, linux-mm@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] mm: slub: Delete useless parameter of alloc_slab_page()
Date: Thu, 10 Mar 2022 09:18:21 +0800 [thread overview]
Message-ID: <CAEVVKH-YbqE_dicLvFG8py0W6tFVEiFwsx_OUcnbv=u4ASkEUQ@mail.gmail.com> (raw)
In-Reply-To: <7c116655-a4ce-5f61-2d98-e85c31e11184@google.com>
On Thu, Mar 10, 2022 at 1:15 AM David Rientjes <rientjes@google.com> wrote:
>
> On Wed, 9 Mar 2022, Matthew Wilcox wrote:
>
> > On Wed, Mar 09, 2022 at 10:50:52PM +0800, sxwjean@me.com wrote:
> > > From: Xiongwei Song <sxwjean@gmail.com>
> > >
> > > The parameter @s is useless for alloc_slab_page(), let's delete it.
> >
> > Perhaps we could add a little more information here.
> >
> > It was added in 2014 by 5dfb41750992 ("sl[au]b: charge slabs to kmemcg
> > explicitly"). The need for it was removed in 2020 by 1f3147b49d75
> > ("mm: slub: call account_slab_page() after slab page initialization").
> >
> > Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> >
>
> Acked-by: David Rientjes <rientjes@google.com>
Thank you!
next prev parent reply other threads:[~2022-03-10 1:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 14:50 [PATCH 0/2] Cleanups for slab sxwjean
2022-03-09 14:50 ` [PATCH 1/2] mm: slab: Delete unused SLAB_DEACTIVATED flag sxwjean
2022-03-09 17:14 ` David Rientjes
2022-03-10 1:18 ` Xiongwei Song
2022-03-10 1:49 ` Roman Gushchin
2022-03-09 14:50 ` [PATCH 2/2] mm: slub: Delete useless parameter of alloc_slab_page() sxwjean
2022-03-09 15:28 ` Matthew Wilcox
2022-03-09 17:15 ` David Rientjes
2022-03-10 1:18 ` Xiongwei Song [this message]
2022-03-10 1:17 ` Xiongwei Song
2022-03-10 1:48 ` Roman Gushchin
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='CAEVVKH-YbqE_dicLvFG8py0W6tFVEiFwsx_OUcnbv=u4ASkEUQ@mail.gmail.com' \
--to=sxwjean@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=guro@fb.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=sxwjean@me.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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