From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH 0/2] slab bulk alloc/free cleanups
Date: Wed, 20 Jul 2022 16:16:21 +0200 [thread overview]
Message-ID: <5664a855-12de-cad6-e9e9-cc2abcfa1fe2@kernel.org> (raw)
In-Reply-To: <20220614152635.23353-1-42.hyeyoo@gmail.com>
On 6/14/22 17:26, Hyeonggon Yoo wrote:
> This makes SLUB and SLAB use their own kmem_cache_free_bulk()
> (instead of __kmem_cache_free_bulk()) when kmem_cache_alloc_bulk() failed.
> And then it moves generic __kmem_cache_{alloc,free}_bulk to SLOB.
>
> This is suggested by Matthew WilCox.
>
> Hyeonggon Yoo (2):
> mm/sl[au]b: use own bulk free function when bulk alloc failed
> mm/slab_common: move generic bulk alloc/free functions to SLOB
Thanks, pushed to slab/for-5.20/bulk_cleanup
> mm/slab.c | 2 +-
> mm/slab.h | 9 ---------
> mm/slab_common.c | 27 ---------------------------
> mm/slob.c | 25 +++++++++++++++++++++----
> mm/slub.c | 4 ++--
> 5 files changed, 24 insertions(+), 43 deletions(-)
>
prev parent reply other threads:[~2022-07-20 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 15:26 [PATCH 0/2] slab bulk alloc/free cleanups Hyeonggon Yoo
2022-06-14 15:26 ` [PATCH 1/2] mm/sl[au]b: use own bulk free function when bulk alloc failed Hyeonggon Yoo
2022-06-14 15:26 ` [PATCH 2/2] mm/slab_common: move generic bulk alloc/free functions to SLOB Hyeonggon Yoo
2022-07-20 14:16 ` Vlastimil Babka (SUSE) [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=5664a855-12de-cad6-e9e9-cc2abcfa1fe2@kernel.org \
--to=vbabka@kernel.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).