From: Josef Bacik <email@example.com>
Cc: firstname.lastname@example.org, email@example.com,
Subject: LSF/MM/BPF: 2023: Call for Proposals
Date: Fri, 6 Jan 2023 10:50:46 -0500 [thread overview]
Message-ID: <Y7hDVliKq+PzY1yY@localhost.localdomain> (raw)
The annual Linux Storage, Filesystem, Memory Management, and BPF
(LSF/MM/BPF) Summit for 2023 will be held from May 8 to May 10 at the
Vancouver Convention Center in Vancouver, British Columbia, Canada.
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 2023 will be a three day, stand-alone conference with four
subsystem-specific tracks, cross-track discussions, as well as BoF and
On behalf of the committee I am issuing a call for agenda proposals
that are suitable for cross-track discussion as well as technical
subjects for the breakout sessions.
If advance notice is required for visa applications then please point
that out in your proposal or request to attend, and submit the topic as
soon as possible.
We're asking that you please let us know you want to be invited by March
1, 2023. We realize that travel is an ever changing target, but it
helps us get an idea of possible attendance numbers. Clearly things can
and will change, so consider the request to attend deadline more about
planning and less about concrete plans.
1) Fill out the following Google form to request attendance and
suggest any topics
In previous years we have accidentally missed people's attendance
requests because they either didn't cc lsf-pc@ or we simply missed them
in the flurry of emails we get. Our community is large and our
volunteers are busy, filling this out will help us make sure we don't
2) Proposals for agenda topics should still be sent to the following
lists to allow for discussion among your peers. This will help us
figure out which topics are important for the agenda.
and CC the mailing lists that are relevant for the topic in question:
Please tag your proposal with [LSF/MM/BPF TOPIC] to make it easier to
track. In addition, please make sure to start a new thread for each
topic rather than following up to an existing one. Agenda topics and
attendees will be selected by the program committee, but the final
agenda will be formed by consensus of the attendees on the day.
3) This year we would like to try and make sure we are including new
members in the community that the program committee may not be familiar
with. 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, but additionally if maintainers or long
term community members could add nominees to the form it would help us
make sure that new members get the proper consideration.
For discussion leaders, slides and visualizations are encouraged to
outline the subject matter and focus the discussions. Please refrain
from lengthy presentations and talks; the sessions are supposed to be
interactive, inclusive discussions.
The COVID related restrictions can be found here, however at this time
there are no protocols defined.
We are still looking into the virtual component. We will likely run
something similar to what we did in 2022, but details on that will be
3) If you have feedback on last year's meeting that we can use to
improve this year's, please also send that to:
Thank you on behalf of the program committee:
Josef Bacik (Filesystems)
Amir Goldstein (Filesystems)
Martin K. Petersen (Storage)
Javier González (Storage)
Michal Hocko (MM)
Dan Williams (MM)
Martin KaFai Lau (BPF)
Daniel Borkmann (BPF)
reply other threads:[~2023-01-06 15:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).