From: "Darrick J. Wong" <djwong@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Amir Goldstein <amir73il@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Luis Chamberlain <mcgrof@kernel.org>,
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>, Jan Kara <jack@suse.cz>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: Re: [Lsf-pc] XFS BoF at LSFMM
Date: Mon, 13 May 2024 15:33:55 -0700 [thread overview]
Message-ID: <20240513223355.GQ2049409@frogsfrogsfrogs> (raw)
In-Reply-To: <20240513134816.GB520598@mit.edu>
On Mon, May 13, 2024 at 07:48:16AM -0600, Theodore Ts'o wrote:
> On Thu, May 09, 2024 at 10:47:45AM -0700, Darrick J. Wong wrote:
> > > > Ritesh and Ted and Jan and I were chatting during the ext4 concall just
> > > > now. Could we have a 30 minute iomap bof at 2:30pm followed by the XFS
> > > > bof after that? That would give us some time to chat with hch about
> > > > iomap (and xfs) direction before he has to leave.
> > > >
> > > > Alternately, we could announce a lunchtime discussion group on Monday
> > > > following Ritesh's presentation about iomap. That could fit everyone's
> > > > schedule better? Also everyone's braincaches will likely be warmer.
> > >
> > > Seems to me that there will be a wider interest in iomap BoF
> > > Not sure what you mean by lunchtime discussion.
> >
> > Monday 90-minute lunch is posted as being in "Grand ballroom C", so I
> > would tell everyone to come find the table(s) I'm sitting at for a
> > discussion over lunch. We can move out to a hallway after everyone's
> > done eating.
> >
> > > We can move Willy's GFP_NOFS talk to 15:30 and have the iomap BoF
> > > after Ritesh's session.
> >
> > <shrug> If you like, though I don't think it's totally necessary. But
> > you might have a better idea of what the venue is like than I do, so
> > I'll let you make that call. :)
>
> How did we decide to resolve this? If we have the iomap BOF at
> 2:30pm, with a hard stop at 3:00pm, that would work for everyone
> including Cristoph.
>
> Or we can try to get all of the people interested in talking about
> iomap at lunch on Wednesday.
It's currently scheduled for 12:30 (Mountain Time, or GMT -0600) tomorrow the
14th. Schedule still subject to change tho
https://docs.google.com/spreadsheets/d/176LXLys9Uh6A-Eal2flrzcbUSJMUXGkGwyihr9jAAaQ/edit#gid=0
--D
> Or we could do something that requires a lot more juggling of slots,
> which I'll leave to the track leads. :-)
>
> All of these ideas work for me.
>
>
> As far as scheduling per-file system BOF's, I'd like to claim the slot
> immediately after XFS for an ext4 BOF, it that would be OK.
>
> Thanks,
>
> - Ted
next prev parent reply other threads:[~2024-05-13 22:33 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 ` [Lsf-pc] " Amir Goldstein
2024-05-09 5:05 ` 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 [this message]
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=20240513223355.GQ2049409@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--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 \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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).