linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Linux-MM layout <linux-mm@kvack.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	Mike Rapoport <rppt@kernel.org>
Subject: [CFP LPC 2022] Kernel Memory Management Microconference
Date: Tue, 24 May 2022 22:48:56 +0200	[thread overview]
Message-ID: <d24e9ac9-0903-3c15-c446-2962f44a360f@suse.cz> (raw)

Hi,

this year there will be a brand new

	Kernel Memory Management Microconference

co-lead by Matthew Wilcox and myself at the Linux Plumbers Conference
(LPC), September 12-14, Dublin, Ireland, or remotely.

This microconference supplements the recently concluded LSF/MM event
by providing an opportunity to discuss current topics with a different
audience, in a different location, and at a different time of year.
We would like to discuss current problems in memory management,
for example:

	* Multi-generational LRU vs traditional LRU

	* Do we need three different slab allocators?

	* How far do we take the folio conversion?

	* Can we handle page pinning and page mapcount more
	  effectively?

	* How can we effectively cache reflinked files?

	* Can we support 1GB pages other than through hugetlbfs?

	* How should we handle memory failures better?

Please submit your proposals at:

	https://lpc.events/event/16/abstracts/

and select "Kernel Memory Management MC" as the track.
Please do that by the 1st of July to allow us to plan the schedule on time.

We're looking forward to your proposals and seeing you either in Dublin
or virtually!

Thanks,
Vlastimil


             reply	other threads:[~2022-05-24 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 20:48 Vlastimil Babka [this message]
2022-06-27 10:43 ` 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=d24e9ac9-0903-3c15-c446-2962f44a360f@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