From: Mike Rapoport <mike.rapoport@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Pekka Enberg <penberg@kernel.org>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, rcu@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, netdev@vger.kernel.org,
linux-doc@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Frederic Weisbecker <frederic@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Jonathan Corbet <corbet@lwn.net>,
Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mike Rapoport <rppt@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Paolo Abeni <pabeni@redhat.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 0/7] remove SLOB and allow kfree() with kmem_cache_alloc()
Date: Sun, 12 Mar 2023 11:51:29 +0200 [thread overview]
Message-ID: <ZA2gofYkXRcJ8cLA@kernel.org> (raw)
In-Reply-To: <20230310103210.22372-1-vbabka@suse.cz>
Hi Vlastimil,
On Fri, Mar 10, 2023 at 11:32:02AM +0100, Vlastimil Babka wrote:
> Also in git:
> https://git.kernel.org/vbabka/h/slab-remove-slob-v1r1
>
> The SLOB allocator was deprecated in 6.2 so I think we can start
> exposing the complete removal in for-next and aim at 6.4 if there are no
> complaints.
>
> Besides code cleanup, the main immediate benefit will be allowing
> kfree() family of function to work on kmem_cache_alloc() objects (Patch
> 7), which was incompatible with SLOB.
>
> This includes kfree_rcu() so I've updated the comment there to remove
> the mention of potential future addition of kmem_cache_free_rcu() as
> there should be no need for that now.
>
> Otherwise it's straightforward. Patch 2 is a cleanup in net area, that I
> can either handle in slab tree or submit in net after SLOB is removed.
> Another cleanup in tomoyo is already in the tomoyo tree as that didn't
> need to wait until SLOB removal.
>
> Vlastimil Babka (7):
> mm/slob: remove CONFIG_SLOB
> net: skbuff: remove SLOB-specific ifdefs
> mm, page_flags: remove PG_slob_free
> mm, pagemap: remove SLOB and SLQB from comments and documentation
> mm/slab: remove CONFIG_SLOB code from slab common code
> mm/slob: remove slob.c
> mm/slab: document kfree() as allowed for kmem_cache_alloc() objects
>
> Documentation/admin-guide/mm/pagemap.rst | 6 +-
> Documentation/core-api/memory-allocation.rst | 15 +-
> fs/proc/page.c | 5 +-
> include/linux/page-flags.h | 4 -
> include/linux/rcupdate.h | 6 +-
> include/linux/slab.h | 39 -
> init/Kconfig | 2 +-
> kernel/configs/tiny.config | 1 -
> mm/Kconfig | 22 -
> mm/Makefile | 1 -
> mm/slab.h | 61 --
> mm/slab_common.c | 7 +-
> mm/slob.c | 757 -------------------
> net/core/skbuff.c | 16 -
> tools/mm/page-types.c | 6 +-
> 15 files changed, 23 insertions(+), 925 deletions(-)
> delete mode 100644 mm/slob.c
git grep -in slob still gives a couple of matches. I've dropped the
irrelevant ones it it left me with these:
CREDITS:14:D: SLOB slab allocator
kernel/trace/ring_buffer.c:358: * Also stolen from mm/slob.c. Thanks to Mathieu Desnoyers for pointing
mm/Kconfig:251: SLOB allocator and is not recommended for systems with more than
mm/Makefile:25:KCOV_INSTRUMENT_slob.o := n
Except the comment in kernel/trace/ring_buffer.c all are trivial.
As for the comment in ring_buffer.c, it looks completely irrelevant at this
point.
@Steve?
> --
> 2.39.2
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-03-12 9:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 10:32 [PATCH 0/7] remove SLOB and allow kfree() with kmem_cache_alloc() Vlastimil Babka
2023-03-10 10:32 ` [PATCH 1/7] mm/slob: remove CONFIG_SLOB Vlastimil Babka
2023-03-14 7:18 ` Hyeonggon Yoo
2023-03-14 22:11 ` Lorenzo Stoakes
2023-03-10 10:32 ` [PATCH 2/7] net: skbuff: remove SLOB-specific ifdefs Vlastimil Babka
2023-03-10 10:32 ` [PATCH 3/7] mm, page_flags: remove PG_slob_free Vlastimil Babka
2023-03-14 7:25 ` Hyeonggon Yoo
2023-03-14 22:12 ` Lorenzo Stoakes
2023-03-10 10:32 ` [PATCH 4/7] mm, pagemap: remove SLOB and SLQB from comments and documentation Vlastimil Babka
2023-03-14 8:19 ` Hyeonggon Yoo
2023-03-15 11:05 ` Vlastimil Babka
2023-03-14 22:16 ` Lorenzo Stoakes
2023-03-10 10:32 ` [PATCH 5/7] mm/slab: remove CONFIG_SLOB code from slab common code Vlastimil Babka
2023-03-14 9:28 ` Hyeonggon Yoo
2023-03-14 22:16 ` Lorenzo Stoakes
2023-03-10 10:32 ` [PATCH 6/7] mm/slob: remove slob.c Vlastimil Babka
2023-03-14 9:34 ` Hyeonggon Yoo
2023-03-14 22:18 ` Lorenzo Stoakes
2023-03-15 2:54 ` Roman Gushchin
2023-03-10 10:32 ` [PATCH 7/7] mm/slab: document kfree() as allowed for kmem_cache_alloc() objects Vlastimil Babka
2023-03-12 9:59 ` Mike Rapoport
2023-03-15 13:38 ` Vlastimil Babka
2023-03-15 14:50 ` Mike Rapoport
2023-03-11 1:00 ` [PATCH 0/7] remove SLOB and allow kfree() with kmem_cache_alloc() Jakub Kicinski
2023-03-12 9:51 ` Mike Rapoport [this message]
2023-03-13 16:31 ` Steven Rostedt
2023-03-13 18:00 ` Mike Rapoport
2023-03-15 13:53 ` Vlastimil Babka
2023-03-15 14:20 ` Steven Rostedt
2023-03-15 14:22 ` Vlastimil Babka
2023-03-13 16:36 ` Vlastimil Babka
2023-03-14 22:10 ` Lorenzo Stoakes
2023-03-15 13:40 ` Vlastimil Babka
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=ZA2gofYkXRcJ8cLA@kernel.org \
--to=mike.rapoport@gmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patches@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=penberg@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.