From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 42D07C2BB48 for ; Tue, 15 Dec 2020 13:43:18 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id DB15922515 for ; Tue, 15 Dec 2020 13:43:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DB15922515 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 42AF36B0068; Tue, 15 Dec 2020 08:43:17 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 3B4D86B006C; Tue, 15 Dec 2020 08:43:17 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 22FB76B006E; Tue, 15 Dec 2020 08:43:17 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0176.hostedemail.com [216.40.44.176]) by kanga.kvack.org (Postfix) with ESMTP id 07D646B0068 for ; Tue, 15 Dec 2020 08:43:17 -0500 (EST) Received: from smtpin12.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id BCFE7180AD837 for ; Tue, 15 Dec 2020 13:43:16 +0000 (UTC) X-FDA: 77595633192.12.offer66_3c123fa27423 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin12.hostedemail.com (Postfix) with ESMTP id 9A43518023F64 for ; Tue, 15 Dec 2020 13:43:16 +0000 (UTC) X-HE-Tag: offer66_3c123fa27423 X-Filterd-Recvd-Size: 6166 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf36.hostedemail.com (Postfix) with ESMTP for ; Tue, 15 Dec 2020 13:43:15 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id ACC30AC7F; Tue, 15 Dec 2020 13:43:14 +0000 (UTC) Subject: Re: [LSFMMBPF 2021] A status update To: Michal Hocko , Matthew Wilcox Cc: Josef Bacik , Btrfs BTRFS , "linux-ext4@vger.kernel.org" , Linux FS Devel , "bpf@vger.kernel.org" , "linux-xfs@vger.kernel.org" , Linux Kernel Mailing List , "linux-block@vger.kernel.org" , "linux-scsi@vger.kernel.org" , "linux-mm@kvack.org" , "linux-nvme@vger.kernel.org" References: <20201212172957.GE2443@casper.infradead.org> <20201215122307.GN32193@dhcp22.suse.cz> From: Hannes Reinecke Message-ID: Date: Tue, 15 Dec 2020 14:43:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: <20201215122307.GN32193@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 12/15/20 1:23 PM, Michal Hocko wrote: > On Sat 12-12-20 17:29:57, Matthew Wilcox wrote: >> On Fri, Dec 04, 2020 at 10:48:53AM -0500, Josef Bacik wrote: >>> We on the program committee hope everybody has been able to stay safe= and >>> healthy during this challenging time, and look forward to being able = to see >>> all of you in person again when it is safe. >>> >>> The current plans for LSFMMBPF 2021 are to schedule an in person conf= erence >>> in H2 (after June) of 2021. The tentative plan is to use the same ho= tel >>> that we had planned to use for 2020, as we still have contracts with = them. >>> However clearly that is not set in stone. The Linux Foundation has d= one a >>> wonderful job of working with us to formulate a plan and figure out t= he >>> logistics that will work the best for everybody, I really can't thank= them >>> enough for their help. >> >> Thank you all for doing your best in the face of this disruption. I >> really appreciate all the work you're putting in, and I can't wait to >> see you all again in person. >> >> I hosted a Zoom call yesterday on the topic of Page Folios, and upload= ed >> the video. >=20 > Thanks for organizing this. I couldn't attent directly but I have > watched the video. I think this was a useful meeting. >=20 >> There was interest expressed in the call on doing a follow-up >> call on the topic of GUP (get_user_pages and friends). It would proba= bly >> also be good to have meetings on other topics. >=20 > I hope I will have time to join this one. >=20 >> I don't want this to be seen in any way as taking away from LSFMMBPF. >> I see Zoom calls as an interim solution to not having face-to-face >> meetings. >=20 > Agreed! >=20 >> I'd like to solicit feedback from this group on: >> >> - Time of day. There is no good time that suits everyone around >> the world. With developers in basically every inhabited time zone= , the >> call will definitely take place in the middle of somebody's night,= and >> during somebody else's normal family time. Publishing the recordi= ngs >> helps ameliorate some of this, but I feel we should shift the time >> around. Having it at the same time of day helps people fit it int= o >> their schedule of other meetings (and meals), but I think the bene= fits >> of allowing more people to participate live outweighs the costs. >=20 > Hard question without any good answer. You can rotate preferred timezon= e > which should spread the suffering. >=20 What I found useful is to have a fixed schedule for the actual talk, but=20 keep the recording online for an extended time (say 24h). And require=20 the presenters to be available in a break-out room for any questions for=20 an extended time, too. That way any participant can choose which time would suit him best to=20 watch the presentation, _and_ being reasonably sure that he can fire up=20 questions later on. >> - Schedule. Friday's probably a bad day to have it, as it ends up >> being Saturday for some people. It can move around the week too. >> Also, probably wise to not have it over Christmas as most develope= rs >> have that period as family time. >=20 > Yes, Friday tends to be not great. I think mid week should work better > as the overalap >=20 >> - Topics. I'm sure there's no shortage of things to discuss! I'm >> happy to organise meetings for people even on topics I have no dir= ect >> interest in. >=20 > Thanks for organizing this. I am pretty sure poeple will land on topics > either in the call or over email. >=20 >> And most urgently, when should we have the GUP meeting? On the call, >> I suggested Friday the 8th of January, but I'm happy to set something >> up for next week if we'd like to talk more urgently. >=20 > I am unlikely to be able to join before the end of year so if you ask > me. >=20 > Thanks again and fingers crossed we can actually have a face to face > meeting sometimes during next year. >=20 I'd side with Michal here; having something this year will be=20 challenging, as quite some ppl (myself included) will be on holiday. Rather move it to start of next year; mid-February would be a good time,=20 giving enough room to organize etc. Cheers, Hannes --=20 Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg HRB 36809 (AG N=C3=BCrnberg), Gesch=C3=A4ftsf=C3=BChrer: Felix Imend=C3=B6= rffer