From: Al Viro <viro@zeniv.linux.org.uk>
To: Matthew Wilcox <willy@infradead.org>
Cc: Josef Bacik <josef@toxicpanda.com>,
lsf-pc <lsf-pc@lists.linuxfoundation.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org, linux-xfs@vger.kernel.org,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
bpf@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [LSFMMBPF TOPIC] Killing LSFMMBPF
Date: Fri, 6 Mar 2020 17:04:17 +0000 [thread overview]
Message-ID: <20200306170417.GX23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200306160548.GB25710@bombadil.infradead.org>
On Fri, Mar 06, 2020 at 08:05:48AM -0800, Matthew Wilcox wrote:
> > 4) Presentations. 90% of the conference is 1-2 people standing at the front
> > of the room, talking to a room of 20-100 people, with only a few people in
> > the audience who cares. We do our best to curate the presentations so we're
> > not wasting peoples time, but in the end I don't care what David Howells is
> > doing with mount, I trust him to do the right thing and he really just needs
> > to trap Viro in a room to work it out, he doesn't need all of us.
>
> ... and allow the other 3-5 people who're interested or affected the
> opportunity to sit in. Like a mailing list, but higher bandwidth.
Latency can be more unpleasant, actually - you try to discuss something between
3 people, when one is in .uk, another - in .us (east coast) and the third one -
in ,au (also east coast). Timezone deltas - 5 hours and 8 hours, in opposite
directions... Incidentally, that was about mount, with me and David being
two of participants; I somewhat hoped to get that sorted out at LSF, but Ian
won't be there anyway. OTOH, that's just an 8 hours delta...
next prev parent reply other threads:[~2020-03-06 17:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 14:35 [LSFMMBPF TOPIC] Killing LSFMMBPF Josef Bacik
2020-03-06 15:29 ` Jason Gunthorpe
2020-03-06 15:30 ` [Lsf-pc] " Amir Goldstein
2020-03-06 15:55 ` Josef Bacik
2020-03-06 15:56 ` Theodore Y. Ts'o
2020-03-06 16:08 ` Josef Bacik
2020-03-06 19:48 ` Theodore Y. Ts'o
2020-03-06 18:30 ` Rik van Riel
2020-03-07 18:54 ` [LSFMMBPF TOPIC] LSFMMBPF 2020 COVID-19 status update Luis Chamberlain
2020-03-07 19:00 ` Josef Bacik
2020-03-07 19:12 ` James Bottomley
2020-03-06 16:04 ` [LSFMMBPF TOPIC] Killing LSFMMBPF Nikolay Borisov
2020-03-06 16:05 ` Matthew Wilcox
2020-03-06 17:04 ` Al Viro [this message]
2020-03-06 17:37 ` James Bottomley
2020-03-06 18:06 ` Jason Gunthorpe
2020-03-06 19:07 ` Martin K. Petersen
2020-03-06 19:15 ` James Bottomley
2020-03-06 19:20 ` Martin K. Petersen
2020-03-06 18:23 ` Matthew Wilcox
2020-03-06 19:25 ` James Bottomley
2020-03-06 16:15 ` James Bottomley
2020-03-06 16:28 ` Christian Brauner
2020-03-06 16:31 ` Josef Bacik
2020-03-06 19:27 ` [LSFMMBPF TOPIC] long live LFSMMBPF Chris Mason
2020-03-06 19:41 ` James Bottomley
2020-03-06 19:56 ` Chris Mason
2020-03-06 20:25 ` Theodore Y. Ts'o
2020-03-07 3:14 ` [LSFMMBPF TOPIC] Killing LSFMMBPF Steve French
2020-03-10 13:13 ` Michal Hocko
2020-03-10 13:40 ` Josef Bacik
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=20200306170417.GX23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bpf@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).