mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Christian Brauner <brauner@kernel.org>,
	lsf-pc@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Kanchan Joshi <joshi.k@samsung.com>,
	"Martin K. Petersen" <mkp@kernel.org>,
	Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
	Vlastimil Babka <vbabka@kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>
Subject: LSF/MM/BPF: 2027: Call for Proposals
Date: Thu, 19 Nov 2026 14:33:58 +0100	[thread overview]
Message-ID: <20261119-lsfmm-2027-cfp-b7edcf7eee48@brauner> (raw)

The annual Linux Storage, Filesystem, Memory Management, and BPF
(LSF/MM/BPF) Summit for 2027 will be held April 27-29, 2027 in Porto,
Portugal.

LSF/MM/BPF is a small, invitation-only technical workshop for the
people who develop and maintain the Linux storage, filesystem, memory
management, and BPF subsystems. We get together to work through
problems and to map out improvements that will make their way into the
mainline kernel within the coming years.

The summit runs for three days and has four subsystem-specific tracks.
Topics that touch more than one subsystem get joint sessions with all
affected tracks in the room. You're welcome to sit in on sessions of
other tracks too. There's also time for BoFs, hacking sessions and the
hallway track.

The sessions are supposed to be interactive, inclusive discussions. The
discussion leader outlines the problem and then the room works through
it. Slides and visualizations are encouraged but please refrain from
lengthy presentations.

The agenda is built from the topics proposed on the mailing lists. The
discussion a proposal gets on the list helps us figure out which topics
are important. The program committee then selects the topics and sends
out the invitations.

Attendance is limited to keep the sessions productive. When you request
an invitation, please tell us what you'd like to discuss and what
expertise you bring. We also want to make sure that people who are new
to the community get proper consideration. So if you're a maintainer or
have been around for a while, please nominate newer contributors in the
form.

LSF/MM/BPF is an in-person event and we don't offer general remote
participation. If you're needed for a topic but can't travel, let us
know and we'll try to find a solution.

Important dates
===============

    January 27, 2027    Deadline for invitation requests
    Mid-February        First round of invitations
    April 27-29, 2027   LSF/MM/BPF 2027 in Porto, Portugal

Venue
=====

The event will take place at the 

    Sheraton Porto Hotel & Spa
    R. do Ten. Valadim 146
    4100-476 Porto, Portugal

Do note that for this years iteration it is of the utmost importance
that you make use of the Linux Foundation hotel block.

All further details are availabe on the event site:

    https://events.linuxfoundation.org/lsfmmbpf/

Requesting an invitation
========================

To attend, please fill out this form by January 27, 2027. Proposing a
topic on the list without filling out the form will lead to us discussing
it without you!

    https://forms.gle/hhC9zXMsAJCR2dda6

In the form, please tell us:

    - what general areas you'd like to discuss and what expertise you bring
    - whether you need a visa. We handle those requests in the first
      round of invitations, so please don't wait.

We realize that travel is an ever-changing target, but the requests
help us get an idea of possible attendance numbers.

Proposing a topic
=================

In addition to the form, please send each topic as a new thread with
[LSF/MM/BPF TOPIC] in the subject to:

    lsf-pc@lists.linux-foundation.org

and Cc the lists that are relevant for the topic:

    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

Please use exactly this subject prefix so we can find the topic
proposals when putting together the schedule. The mailing list
discussions will be linked from the schedule so other attendees can get
a sense of whether a topic is of interest to them.

Previous years
==============

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/
    2026: https://lwn.net/Articles/lsfmmbpf2026/

Program committee
=================

    Kanchan Joshi      (Storage)
    Martin K. Petersen (Storage)
    Christian Brauner  (Filesystems)
    Amir Goldstein     (Filesystems)
    Jan Kara           (Filesystems)
    Vlastimil Babka    (MM)
    Matthew Wilcox     (MM)
    Daniel Borkmann    (BPF)
    Alexei Starovoitov (BPF)

Thank you,
Christian Brauner

                 reply	other threads:[~2026-11-19 13: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=20261119-lsfmm-2027-cfp-b7edcf7eee48@brauner \
    --to=brauner@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jack@suse.cz \
    --cc=joshi.k@samsung.com \
    --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 \
    --cc=mkp@kernel.org \
    --cc=vbabka@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

all inboxes | Powered by JetHome®