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=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 E922EC32771 for ; Wed, 15 Jan 2020 21:54:13 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id A69B72081E for ; Wed, 15 Jan 2020 21:54:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=toxicpanda-com.20150623.gappssmtp.com header.i=@toxicpanda-com.20150623.gappssmtp.com header.b="KePd9Zfq" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A69B72081E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=toxicpanda.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 41A348E000B; Wed, 15 Jan 2020 16:54:13 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 3CAA18E0003; Wed, 15 Jan 2020 16:54:13 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 2BA258E000B; Wed, 15 Jan 2020 16:54:13 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0038.hostedemail.com [216.40.44.38]) by kanga.kvack.org (Postfix) with ESMTP id 0A6CB8E0003 for ; Wed, 15 Jan 2020 16:54:13 -0500 (EST) Received: from smtpin16.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with SMTP id B67362C93 for ; Wed, 15 Jan 2020 21:54:12 +0000 (UTC) X-FDA: 76381222344.16.bit51_24b0fe5a49703 X-HE-Tag: bit51_24b0fe5a49703 X-Filterd-Recvd-Size: 7559 Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) by imf23.hostedemail.com (Postfix) with ESMTP for ; Wed, 15 Jan 2020 21:54:12 +0000 (UTC) Received: by mail-qt1-f181.google.com with SMTP id w47so17175151qtk.4 for ; Wed, 15 Jan 2020 13:54:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toxicpanda-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :content-transfer-encoding; bh=JtTvNccN+0/+lCGUOatY00GbzmTZrZ9tQej/2dZXgxw=; b=KePd9ZfqDfmOkXqFFTc3Q9LwzsdRxP/xYXtHcwOYE2P45KBCjSc7c09L/RvSjEB3lY QMzCYCg4J138ouYNcOygau/65JCD6GLK9yg6ZujG+wHqgyj6xyoPj6PIg6EXpnaufwh7 Z510eSm16ZQQlyVQUQ6H4u455OeTZzrZoL2cHWu/2KDD55t3Dg3KPfSsFqOK1sG2ro6C wpw0NoTRojtNoZ1Mm/O6vJrSogBMAqYbLVyoBo6in2wt4xTkU/Q6oi+gH+1liu+6xGtu DNYenwCawyAjhSHWPmBnnZtQIznYZmw6UFDfQNPmBQgDGs4Z4KR8S2bmvh8uklxplGW+ 9kVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:content-transfer-encoding; bh=JtTvNccN+0/+lCGUOatY00GbzmTZrZ9tQej/2dZXgxw=; b=DrkzYVtm9fjadZARK11nL2AFsamZMzltyhQkLK/o7c+MH0Um3C7O5ejblB6Bisyfy2 qkxbByCVqPNV/O7AnijNK660zfYBV38AeB8Iws8VyQI8GLRL2b6tCIRb7IcrLWI82kcY +z2D0n7JP5m+oyqhukZc4A/xOSeYAWN8Tp0Gv505BZgcK/NnjblqYdoErthUqnQwdk9H O82ymbJv5KfMUmQ9uI4TbYGcCKjdp8WQd2SG1sp3Dg+notQQKYflidbe2jt0mj+XS5ul 4AsyaV9o5dyN0zHBpHg7m5uTkXEahcC/lebneWAWWvaos/e3/BIJBpANJFUF/higCSpH 00eA== X-Gm-Message-State: APjAAAUhd9UdUtwDXTQvEgABbiXf0mJ/UPpwiZzdC2/dLqpMH+EyE3dW 8IvZ5iknaBr1gBBahP3umDq1nQ== X-Google-Smtp-Source: APXvYqxcRE3B5iQiFW7B0tOZ3c36MzfvnKAl5xIFQTt35nmhPCQoqb66aA5/hose3wVQiuv4Glt7kQ== X-Received: by 2002:aed:2150:: with SMTP id 74mr707121qtc.323.1579125251168; Wed, 15 Jan 2020 13:54:11 -0800 (PST) Received: from localhost ([107.15.81.208]) by smtp.gmail.com with ESMTPSA id g21sm9058033qkl.116.2020.01.15.13.54.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Jan 2020 13:54:10 -0800 (PST) Date: Wed, 15 Jan 2020 16:54:09 -0500 From: Josef Bacik To: lsf-pc , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-block@vger.kernel.org, linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org Subject: REMINDER: LSF/MM/BPF: 2020: Call for Proposals Message-ID: <20200115215409.5pd4fnoawqzs7rvw@jbacik-mbp> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000008, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: This is a reminder that we are still taking requests for this years Linux Storage, Filesystem, Memory Management, and BPF Summit. Below is the ori= ginal announcement but we would like to hilight a few changes and re-iterate a = few things. 1) The venue has been finalized and as such the website is now live https://events.linuxfoundation.org/lsfmm/ 2) Please make sure to fill out the google form to make sure we don't mis= s your request. 3) PLEASE STILL SUBMIT TOPICS TO THE RELEVANT MAILINGLISTS. The topics o= f interest part of the form is so we can figure out what topics from the mailinglist are the relevant discussions to have. If you submit a topic = please feel free to paste a lore link in your form if you've not already filled = out the form. The rest of the details of course are in the original announcment which i= s included below. Thanks, Josef -------------- Original announcement --------------------- The annual Linux Storage, Filesystem, Memory Management, and BPF (LSF/MM/BPF) Summit for 2020 will be held from April 27 - April 29 at The Riviera Palm Springs, A Tribute Portfolio Resort in Palm Springs, California. LSF/MM/BPF is an invitation-only technical workshop to map out improvements to the Linux storage, filesystem, BPF, and memory management subsystems that will make their way into the mainline kernel within the coming years. LSF/MM/BPF 2020 will be a three day, stand-alone conference with four subsystem-specific tracks, cross-track discussions, as well as BoF and hacking sessions. On behalf of the committee I am issuing a call for agenda proposals that are suitable for cross-track discussion as well as technical subjects for the breakout sessions. If advance notice is required for visa applications then please point that out in your proposal or request to attend, and submit the topic as soon as possible. This year will be a little different for requesting attendance. Please do the following by February 15th, 2020. 1) Fill out the following Google form to request attendance and suggest any topics https://forms.gle/voWi1j9kDs13Lyqf9 In previous years we have accidentally missed people's attendance requests because they either didn't cc lsf-pc@ or we simply missed them in the flurry of emails we get. Our community is large and our volunteers are busy, filling this out will help us make sure we don't miss anybody. 2) Proposals for agenda topics should still be sent to the following lists to allow for discussion among your peers. This will help us figure out which topics are important for the agenda. =A0 =A0 =A0 =A0=A0lsf-pc@lists.linux-foundation.org and CC the mailing lists that are relevant for the topic in question: =A0 =A0 =A0 =A0 FS:=A0 =A0 =A0linux-fsdevel@vger.kernel.org =A0 =A0 =A0 =A0 MM:=A0 =A0 =A0linux-mm@kvack.org =A0 =A0 =A0 =A0 Block:=A0=A0linux-block@vger.kernel.org =A0 =A0 =A0 =A0 ATA:=A0 =A0=A0linux-ide@vger.kernel.org =A0 =A0 =A0 =A0 SCSI:=A0 =A0linux-scsi@vger.kernel.org =A0 =A0 =A0 =A0 NVMe:=A0 =A0linux-nvme@lists.infradead.org BPF: bpf@vger.kernel.org Please tag your proposal with [LSF/MM/BPF TOPIC] to make it easier to track. In addition, please make sure to start a new thread for each topic rather than following up to an existing one. Agenda topics and attendees will be selected by the program committee, but the final agenda will be formed by consensus of the attendees on the day. We will try to cap attendance at around 25-30 per track to facilitate discussions although the final numbers will depend on the room sizes at the venue. For discussion leaders, slides and visualizations are encouraged to outline the subject matter and focus the discussions. Please refrain from lengthy presentations and talks; the sessions are supposed to be interactive, inclusive discussions. There will be no recording or audio bridge. However, we expect that written minutes will be published as we did in previous years: 2019:=A0https://lwn.net/Articles/lsfmm2019/ 2018:=A0https://lwn.net/Articles/lsfmm2018/ 2017:=A0https://lwn.net/Articles/lsfmm2017/ 2016:=A0https://lwn.net/Articles/lsfmm2016/ 2015:=A0https://lwn.net/Articles/lsfmm2015/ 2014:=A0http://lwn.net/Articles/LSFMM2014/ 3) If you have feedback on last year's meeting that we can use to improve this year's, please also send that to: =A0 =A0 =A0 =A0=A0lsf-pc@lists.linux-foundation.org Thank you on behalf of the program committee: Josef Bacik (Filesystems) Amir Goldstein (Filesystems) Martin K. Petersen (Storage) Omar Sandoval (Storage) Michal Hocko (MM) Dan Williams (MM) Alexei Starovoitov (BPF) Daniel Borkmann (BPF)