From: Amir Goldstein <amir73il@gmail.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>
Cc: lsf-pc@lists.linux-foundation.org,
xfs <linux-xfs@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Chandan Babu R <chandan.babu@oracle.com>
Subject: Re: [Lsf-pc] XFS BoF at LSFMM
Date: Thu, 9 May 2024 08:01:39 +0300 [thread overview]
Message-ID: <CAOQ4uxj8qVpPv=YM5QiV5ryaCmFeCvArFt0Uqf29KodBdnbOaw@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6V_TqhQ0cqSdnDg7AZZQ5ZqzgBJHuHkjKBK0x_buKsgeQ@mail.gmail.com>
On Wed, May 8, 2024 at 10:42 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> How about an XFS BoF at LSFMM?
Let me rephrase that.
Darrick,
Would you like to list some items for the XFS BoF so I can put it on
the agenda and link to this thread?
> Would it be good to separate the BoF
> for XFS and bcachefs so that folks who want to attend both can do so?
I have set a side 2.5 hours in the schedule on Wed afternoon for per-FS BoF
3 hours if you include the FS lightning slot afterwards that could be used
as per-FS lightning updates.
> How about Wednesday 15:30? That would allow a full hour for bcachefs.
I have no doubt that people want to be updated about bcaches,
but a full hour for bcachefs? IDK.
FYI, I counted more than 10 attendees that are active contributors or
have contributed to xfs in one way or another.
That's roughly a third of the FS track.
So let's see how much time XFS BoF needs and divide the rest of the
time among other FS that want to do a BoF in the FS room.
If anyone would like to run a *FS BoF in the FS room please let me know
and please try to estimate how much time you will need.
You can also "register" for *FS lightning talk, but we can also arrange this
ad-hoc.
Excited to see you all next week!
Thanks,
Amir.
next prev parent reply other threads:[~2024-05-09 5:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 19:41 XFS BoF at LSFMM Luis Chamberlain
2024-05-09 5:01 ` Amir Goldstein [this message]
2024-05-09 5:05 ` [Lsf-pc] " Christoph Hellwig
2024-05-09 5:23 ` Amir Goldstein
2024-05-09 15:55 ` Darrick J. Wong
2024-05-09 15:59 ` Christoph Hellwig
2024-05-09 17:29 ` Amir Goldstein
2024-05-09 17:47 ` Darrick J. Wong
2024-05-13 13:48 ` Theodore Ts'o
2024-05-13 22:33 ` Darrick J. Wong
2024-05-09 9:09 ` Ritesh Harjani
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='CAOQ4uxj8qVpPv=YM5QiV5ryaCmFeCvArFt0Uqf29KodBdnbOaw@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).