From: Vlastimil Babka <vbabka@suse.cz>
To: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
bpf <bpf@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] SLUB: what's next?
Date: Mon, 20 May 2024 22:52:39 +0200 [thread overview]
Message-ID: <f177782d-2bdf-42cd-8763-ce373b216ddb@suse.cz> (raw)
In-Reply-To: <b929d5fb-8e88-4f23-8ec7-6bdaf61f84f9@suse.cz>
On 4/30/24 5:42 PM, Vlastimil Babka wrote:
> Hi,
>
> I'd like to propose a session about the next steps for SLUB. This is
> different from the BOF about sheaves that Matthew suggested, which would be
> not suitable for the whole group due to being not fleshed out enough yet.
> But the session could be scheduled after the BOF so if we do brainstorm
> something promising there, the result could be discussed as part of the full
> session.
Since I've been asked if the slides could be shared, here goes:
https://drive.google.com/file/d/1fHozm2y97Biceh19e_aL5PrHLAZFntZW/view
> Aside from that my preliminary plan is to discuss:
>
> - what was made possible by reducing the slab allocators implementations to
> a single one, and what else could be done now with a single implementation
>
> - the work-in-progress work (for now in the context of maple tree) on SLUB
> per-cpu array caches and preallocation
>
> - what functionality would SLUB need to gain so the extra caching done by
> bpf allocator on top wouldn't be necessary? (kernel/bpf/memalloc.c)
>
> - similar wrt lib/objpool.c (did you even noticed it was added? :)
>
> - maybe the mempool functionality could be better integrated as well?
>
> - are there more cases where people have invented layers outside mm and that
> could be integrated with some effort? IIRC io_uring also has some caching on
> top currently...
>
> - better/more efficient memcg integration?
>
> - any other features people would like SLUB to have?
>
> Thanks,
> Vlastimil
prev parent reply other threads:[~2024-05-20 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 15:42 [LSF/MM/BPF TOPIC] SLUB: what's next? Vlastimil Babka
2024-05-01 9:23 ` Alexei Starovoitov
2024-05-02 7:59 ` [Lsf-pc] " Michal Hocko
2024-05-02 9:26 ` Vlastimil Babka
2024-05-06 21:04 ` Roman Gushchin
2024-05-20 20:52 ` Vlastimil Babka [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=f177782d-2bdf-42cd-8763-ce373b216ddb@suse.cz \
--to=vbabka@suse.cz \
--cc=bpf@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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 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.