From: Vlastimil Babka <vbabka@suse.cz>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [CFP LPC 2024] Kernel Memory Management Microconference
Date: Fri, 31 May 2024 09:34:54 +0200 [thread overview]
Message-ID: <ffc05b5d-9fd0-4926-807f-04f90adff255@suse.cz> (raw)
Hi,
this year there will be another instance of the
Kernel Memory Management Microconference
co-lead by Matthew Wilcox and myself at the Linux Plumbers Conference
(LPC), September 18-20, Vienna, Austria, or remotely.
This microconference supplements the recently concluded LSF/MM event
by providing an opportunity to discuss current topics with a different
audience, on a different continent, and at a different time of year.
We would like to discuss current problems in memory management,
for example:
* Should we add memory policy zones?
* How far should we go to support CXL?
* How do we handle page allocation in a memdesc world?
* Should we switch the slab allocator from partial slabs to sheaves?
* Can we get rid of non-compound multi-page allocations?
* What other improvements might we see from mTHP?
* How might we make allocations guaranteed to not fail?
* Can we share the pagecache between reflinked files?
* Is there a better way to share page tables between processes than hugetlb?
Please submit your proposals at:
https://lpc.events/event/18/abstracts/
and select "Kernel Memory Management MC" as the track.
Please do that by the 5th of July to allow us to plan the schedule on time.
We're looking forward to your proposals and seeing you either in Vienna
or virtually!
Thanks,
Vlastimil
reply other threads:[~2024-05-31 7:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ffc05b5d-9fd0-4926-807f-04f90adff255@suse.cz \
--to=vbabka@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--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