Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp3376263pxu; Tue, 15 Dec 2020 05:45:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJwlsijnGcPxWL6gHrm+jtpoT4WnmfWhpBYgM+3Qp3G4/IQ56YQayZjvt0AJxvuExyHW7pdO X-Received: by 2002:a05:6402:318f:: with SMTP id di15mr29656188edb.237.1608039935167; Tue, 15 Dec 2020 05:45:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608039935; cv=none; d=google.com; s=arc-20160816; b=egINHtgZJul5xZ0G4ajb+n+12Sdl33vJdM5eHCw+MmvCs0deKXfQoodTdlpP7ipdaf ajO9xqXqC0ob5u2hv378cLFHF4nE/wNwOYkB7Ftp0W0vIg2AY4TTjsM3Qk1r9q1krtcp C4O0ithht7P7DUqCE6AFx6TPuwtanXd5W2r0587T9xAqGCTKy8IaxdYVYlk5Od74hj20 N5ky1cfcc3hyXp5NfwyI4l1/LwyHa1mSpGDKzKRSYhAputsbXfg9PHV/JyHzG7PcR1Fg bbTJhdU45VKXTJkOUEDo5A4DozfvCa4ITy4POKFaA9ZHFpPwOSJ9C53OCHgCu/5ox0j+ 5O3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=880zrM4U4a6XdjXENd8HW5/DOhqi5ZqwiRmqXNoDFZI=; b=Ag1H98ZHdsKTt6i6XzhcwnBLQvRx8gRXqEAIhWi3nnpVrEdMgGVwH5z0dUHwA2bsYM yfUDFGByi9h7Ynwjq74Tf6RZnIRXwiZv6xr3F6VMgudcMniekXDU5ZtzBQn11nHHAR0A kXgEfENwcKRwb5ifZA+eMPdmZEk18iIkc8ycAyIWwORjdbvYntmi3Puh92zExslUlSRV y6hh9I80fgT5kPgnwc6a6k+hKX097/YSXG2Ch2I0J1+4B4TVKFp3bY1UYc4rfhRL+wL7 mZ0cVx6oY8JqwiHvX+unUiAGyvGGJLguoqde7saLYkUu0EA1Mfu37XgQm6rnT7MhmFRE Z8gA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u30si908664edb.89.2020.12.15.05.45.04; Tue, 15 Dec 2020 05:45:35 -0800 (PST) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727925AbgLONn5 (ORCPT + 99 others); Tue, 15 Dec 2020 08:43:57 -0500 Received: from mx2.suse.de ([195.135.220.15]:49184 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727907AbgLONn5 (ORCPT ); Tue, 15 Dec 2020 08:43:57 -0500 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: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org 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 conference >>> in H2 (after June) of 2021. The tentative plan is to use the same hotel >>> 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 done a >>> wonderful job of working with us to formulate a plan and figure out the >>> 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 uploaded >> the video. > > Thanks for organizing this. I couldn't attent directly but I have > watched the video. I think this was a useful meeting. > >> 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 probably >> also be good to have meetings on other topics. > > I hope I will have time to join this one. > >> 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. > > Agreed! > >> 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 recordings >> 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 into >> their schedule of other meetings (and meals), but I think the benefits >> of allowing more people to participate live outweighs the costs. > > Hard question without any good answer. You can rotate preferred timezone > which should spread the suffering. > What I found useful is to have a fixed schedule for the actual talk, but keep the recording online for an extended time (say 24h). And require the presenters to be available in a break-out room for any questions for an extended time, too. That way any participant can choose which time would suit him best to watch the presentation, _and_ being reasonably sure that he can fire up 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 developers >> have that period as family time. > > Yes, Friday tends to be not great. I think mid week should work better > as the overalap > >> - 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 direct >> interest in. > > Thanks for organizing this. I am pretty sure poeple will land on topics > either in the call or over email. > >> 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. > > I am unlikely to be able to join before the end of year so if you ask > me. > > Thanks again and fingers crossed we can actually have a face to face > meeting sometimes during next year. > I'd side with Michal here; having something this year will be 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, giving enough room to organize etc. Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer