From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
bpf@vger.kernel.org
Cc: lsf-pc@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: LSF/MM/BPF: 2026: Call for Proposals
Date: Sat, 10 Jan 2026 14:24:17 +0100 [thread overview]
Message-ID: <20260110-lsfmm-2026-cfp-ae970765d60e@brauner> (raw)
The annual Linux Storage, Filesystem, Memory Management, and BPF
(LSF/MM/BPF) Summit for 2026 will be held May 4–6, 2026 in Zagreb,
Croatia.
LSF/MM/BPF is an invitation-only technical workshop to map out
improvements to the Linux storage, filesystem, BPF, and memory
management subsystems that will make their way into the mainline
kernel within the coming years.
LSF/MM/BPF 2026 will be a three-day, stand-alone conference with four
subsystem-specific tracks, cross-track discussions, as well as BoF and
hacking sessions. Please check out:
https://events.linuxfoundation.org/lsfmmbpf/
for further details on the venue and hotels.
This is a call for proposals for technical topics for this year's event.
We are asking that you please let us know you want to be invited by
February 20, 2026. We realize that travel is an ever-changing target,
but it helps us to get an idea of possible attendance numbers.
(1) Fill out the following Google form to request attendance and
suggest any topics for discussion:
https://forms.gle/hUgiEksr8CA1migCA
If advance notice is required for visa applications, please point
that out in your proposal or request to attend, and submit the topic
as soon as possible.
(2) Please send topics to
lsf-pc@lists.linux-foundation.org
and to the relevant technical audience:
FS: linux-fsdevel@vger.kernel.org
MM: linux-mm@kvack.org
Block: linux-block@vger.kernel.org
ATA: linux-ide@vger.kernel.org
SCSI: linux-scsi@vger.kernel.org
NVMe: linux-nvme@lists.infradead.org
BPF: bpf@vger.kernel.org
(3) Please tag your proposal with [LSF/MM/BPF TOPIC] and ensure that
each topic is a separate thread.
(4) The Google form has an area for people to add required/optional
attendees. Please encourage new members of the community to submit a
request for an invite as well. Maintainers or long-term community
members can add nominees to the form to help make sure that new
members get the proper consideration.
(5) For discussion leaders, slides and visualizations are encouraged to
outline the subject matter and focus the discussions. Please refrain
from lengthy presentations and talks in order for sessions to be
productive; the sessions are supposed to be interactive, inclusive
discussions.
LWN has covered previous iterations of LSF/MM/BPF extensively:
2014: https://lwn.net/Articles/LSFMM2014/
2015: https://lwn.net/Articles/lsfmm2015/
2016: https://lwn.net/Articles/lsfmm2016/
2017: https://lwn.net/Articles/lsfmm2017/
2018: https://lwn.net/Articles/lsfmm2018/
2019: https://lwn.net/Articles/lsfmm2019/
2020: 404 - Cancelled by The Plague
2021: 404 - Cancelled by The Plague
2022: https://lwn.net/Articles/lsfmm2022/
2023: https://lwn.net/Articles/lsfmmbpf2023/
2024: https://lwn.net/Articles/lsfmmbpf2024/
2025: https://lwn.net/Articles/lsfmmbpf2025/
The program committee for this year consists of:
Javier González (Storage)
Martin K. Petersen (Storage)
Christian Brauner (Filesystems)
Amir Goldstein (Filesystems)
Jan Kara (Filesystems)
Vlastimil Babka (MM)
Matthew Wilcox (MM)
Daniel Borkmann (BPF)
Martin KaFai Lau (BPF)
Thank you,
Christian Brauner
reply other threads:[~2026-01-10 13:25 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=20260110-lsfmm-2026-cfp-ae970765d60e@brauner \
--to=brauner@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox