From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1A83741DEEA for ; Mon, 20 Jul 2026 13:04:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784552647; cv=none; b=rOQ/2oERJdP4lQXFGIp/6WHSHgSf7PCzTs2BYsTBLhQgD2pH4raTFMsD4XRdfyWqZ+qADCoODl6j9+VdkEBIMWSX467+xRiI02b5ewiS1jA+ivWeGvvulCfz405OXpbZB6cpaWwWII6Uxi6IjopEYvSa/UK39U1rqHZi278ySJw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784552647; c=relaxed/simple; bh=YRUXyisy3fWsLtojnjLqZ98GvOTY2xgF4+QS2LnfOhs=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=onLrmWu84WmwWAOL0RhpJRNAGfhYBMaJT8GAhBAgspIb2uPPBKMGEbNl5a7rY5+8xCcrKM59p2amZbSuHaMGDAqgaTrMmVWA/iHuHkmNZrYOTnroH33u2xLrPPGLxHxtRqZyxskULuW1pZ2oxGGJJMGlN2SGewqlLOLYGab/ACE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=aBjnSe1d; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="aBjnSe1d" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 46B0B1F00A3A; Mon, 20 Jul 2026 13:04:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784552645; bh=SICMuK0Og2SbVQNzjOkqW0F8oWy8F1pFz/0ehxr0IRE=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=aBjnSe1d7umy7QyWgAaGrXFQYwN+UFq/JRRmb36ntmzZ5yvuVWJPOdP7rj4h3k/6d f4vQwoNK1jS1fLdrwfZaOue1WqOy2LCGptMViuqNddcrm5Jc+wV6llXACBr5d7pWof NLospFh1vtxjjQjNxLL8RP33G/ECbWN+lv46Cw8cUCLXNTQFb0BVoKe+SWcmf3CvHJ ttJSmx3PPDjCNejLV1REAmWJPZ3XpdCovWMdtMZwkGtAgrwzsicTFrxkTmrVUKnr8b QJJf0jR6d7pTRXCanwVL+nvaZ5SepqsbizFbuWWGiHC4tWGcQVBNW2DTYBUBgQTgdx QAnVUOQn7XXVw== Date: Mon, 20 Jul 2026 14:03:50 +0100 From: "Lorenzo Stoakes (ARM)" To: "linux-mm@kvack.org" Cc: "David Hildenbrand (Arm)" , "linux-kernel@vger.kernel.org" , Mike Rapoport , Steven Rostedt Subject: [ANNOUNCE/CFP] LPC 2026 Kernel Memory Management Microconference (reminder) Message-ID: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Just a reminder for everybody to send their proposals in before the deadline on July 24th! :) See below for guidelines. Cheers, Lorenzo On Mon, May 18, 2026 at 11:26:21PM +0200, David Hildenbrand (Arm) wrote: > Hi, > > We are happy to announce yet another instance of the > > Kernel Memory Management Microconference [1] > > Co-lead by Lorenzo Stoakes and myself at the Linux Plumbers Conference > (LPC), October 5-7, Prague, Czechia [2]. > > Due to our past experience with remote presentations, we will only > accept in-person talks, unfortunately. > > We are looking for topics that would be of interest to the kernel > memory-management community. > > We are also interested in topic suggestion from outside the core kernel > community - if you have something interesting to present related to memory > management in userspace, driver code, architectural code or anywhere else that > touches kernel memory management we'd love to hear from you! > > Examples of topics that might be worth discussing this year include: > > * Making (m)THP/large folios first-class citizens > * Supporting gigabyte THPs: allocators, compaction, policies > * Better policies: applying eBPF and friends sensibly in MM > * Polishing memory reclaim: making MGLRU less special > * Ongoing challenges with memdescs conversion > * Can we make device memory less special? > * Letting the kernel manage special-purpose memory > * Improving page promotion/demotion for memory tiering > * Challenges with hypervisor live-update integration > * Towards deprecating hugetlb: mshare, memory reserves > * The future of swap: missing pieces, cleanups, and do we still need zram? > * The future of memcg: new resources, optimizations, and cleanups > * Doing more with less memory (RAM is getting expensive ...) > > Please submit your proposals at: > > https://lpc.events/event/20/abstracts/ > > and select "Kernel Memory Management MC" as the track. > > Please submit your proposals by July 24th to give us time to schedule talks in > advance of the conference. > > We greatly value interaction - talks are meant to be dialogues between the > speaker and the audience. Therefore, plan to leave AT LEAST 1/3 of your slot > (likely 30min, tbd) open for discussion. We intend to be strict about enforcing > this :) > > Please ensure your slides aren't too dense - people take away more when you use > fewer words, and that also helps the discussion! > > We are looking forward to your proposals and seeing you in Prague! > > > Note: make sure to register early, ideally before the announcement of topics. > Usually the conference organizers ensure that all speakers are able to > register, but the conference is very popular and it's been a close run thing in > the past, so registering early is the safest option. > > [1] https://lpc.events/event/20/contributions/2337/ > [2] https://lpc.events/ > > -- > Cheers, > > David >