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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id DCFE4C433EF for ; Thu, 24 Feb 2022 15:59:27 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5F9E48D0002; Thu, 24 Feb 2022 10:59:27 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 5AA9B8D0001; Thu, 24 Feb 2022 10:59:27 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 471528D0002; Thu, 24 Feb 2022 10:59:27 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0147.hostedemail.com [216.40.44.147]) by kanga.kvack.org (Postfix) with ESMTP id 342348D0001 for ; Thu, 24 Feb 2022 10:59:27 -0500 (EST) Received: from smtpin23.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id DB2459F858 for ; Thu, 24 Feb 2022 15:59:26 +0000 (UTC) X-FDA: 79178133132.23.1C97AA8 Received: from mail-qv1-f47.google.com (mail-qv1-f47.google.com [209.85.219.47]) by imf24.hostedemail.com (Postfix) with ESMTP id 39AE6180007 for ; Thu, 24 Feb 2022 15:59:26 +0000 (UTC) Received: by mail-qv1-f47.google.com with SMTP id h13so4260778qvk.12 for ; Thu, 24 Feb 2022 07:59:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toxicpanda-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding; bh=gqOgm8FvfYxrPnxT+G4DW2qNZzJhArG622fIixWhtpg=; b=h5ZN26X5NAmhxjI2cNyZTmm5+2BZQaB4PhQXbBOhwml31PknsRkSxpnie5Pk4e0n8N ucMddJt/VKcrD9FCGE1zCONNj+58mibz9qaTly7ZSs8IOPNpfWSdXIk9bJOyY3v2osKR fbaKNoDJ5JuvmWbPO700vsU0BSR38IoUkcctt81R1wocDgUthuwF+/lFAHdfS3zgLGgC LpHaI3b7NWCQPs6HVwySmgr9xSeRIEpx6+ByISYyqPZ7GlchosjA+y3B47saPKpwOWcA QUFvAm0akg5UlWQlGCmRw+5HXyDvIck88WNhoeWOXMTwVNMR3907iZEJ4Rb23hd08jHx Am1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding; bh=gqOgm8FvfYxrPnxT+G4DW2qNZzJhArG622fIixWhtpg=; b=RvXC1y201SpSiRVfU2btUBx5hVLvm3tOFeRDOadZA0A/OsHzw0DOe+60ez5OvLIEzx d5gs2HbqYPFsaKq6pbX8blac2B19H3JgFNerMKQSn/1rv18u0EDjvhBJ43LdsFsEkQ0/ +xT44+7Ibi3PvNBWSNSY1Oqjl7uL4MkimE418rrLvezFiKykdsfoE13nCexlUEzYXrB2 Eo57x0Q9mSQr2mBcZFebkVKHEXW9gfwGGcM6/1ATBPLGfrd3BUlXfxw6Y+38qhTT4CnE gssmpnT9MpA0WhZxew5oid2u8D18Qq68XLav4wT+Kh5VZW6JO0to8cCzSZpCRN6zJ43S J8hg== X-Gm-Message-State: AOAM533sCqsIiObVNY0cVqF80ayYfT87jM2oyfP4NihAyk4CbwBF9lds Qyr5NQyCWH8lOkiM+heJomTcKw== X-Google-Smtp-Source: ABdhPJyLQ1BrprrPj7Z/ncbZLKkWpbFJ6QCGUwxS4i7cOHcc1fXc5hBuljJyNTFV6nRd3+MQsFxngQ== X-Received: by 2002:ac8:578c:0:b0:2de:7281:6234 with SMTP id v12-20020ac8578c000000b002de72816234mr2991255qta.359.1645718365211; Thu, 24 Feb 2022 07:59:25 -0800 (PST) Received: from localhost (cpe-174-109-172-136.nc.res.rr.com. [174.109.172.136]) by smtp.gmail.com with ESMTPSA id z14sm1739862qtw.56.2022.02.24.07.59.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Feb 2022 07:59:24 -0800 (PST) Date: Thu, 24 Feb 2022 10:59:23 -0500 From: Josef Bacik To: lsf-pc@lists.linuxfoundation.org Cc: 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: 2022: Call for Proposals Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: 39AE6180007 X-Rspam-User: Authentication-Results: imf24.hostedemail.com; dkim=pass header.d=toxicpanda-com.20210112.gappssmtp.com header.s=20210112 header.b=h5ZN26X5; spf=none (imf24.hostedemail.com: domain of josef@toxicpanda.com has no SPF policy when checking 209.85.219.47) smtp.mailfrom=josef@toxicpanda.com; dmarc=none X-Stat-Signature: yq6hqwswch6fpsifhrm5x3uxmmnkad1j X-HE-Tag: 1645718366-625643 Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000314, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: A few updates - The COVID related restrictions can be found here=20 https://events.linuxfoundation.org/lsfmm/attend/health-and-safety/ - We are working on a virtual component, however it will likely not be interactive, likely just a live stream and then an IRC channel to ask questions through. --- Original email --- The annual Linux Storage, Filesystem, Memory Management, and BPF (LSF/MM/BPF) Summit for 2022 will be held from May 2 to May 4 at The Margaritaville Resort Palm Springs 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. COVID is at the front of our minds as we attempt to put together the best and safest conference we can arrange. The logistics of how to hold an in person event will change and evolve as we get closer to the actual date, but rest assured we will do everything recommended by public health officials. LSF/MM/BPF 2022 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 years instructions are similar to our previous attempts. We're asking that you please let us know you want to be invited by March 1, 2022. We realize that travel is an ever changing target, but it helps us get an idea of possible attendance numbers. Clearly things can and will change, so consider the request to attend deadline more about planning and less about concrete plans. 1) Fill out the following Google form to request attendance and suggest any topics https://forms.gle/uD5tbZYGpaRXPnE19 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.=A0 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.=A0 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 =A0 =A0 =A0 =A0 BPF:=A0 =A0=A0bpf@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: =A0 =A0 =A0 =A0 Josef Bacik (Filesystems) =A0 =A0 =A0 =A0 Amir Goldstein (Filesystems) =A0 =A0 =A0 =A0 Martin K. Petersen (Storage) =A0 =A0 =A0 =A0 Omar Sandoval (Storage) =A0 =A0 =A0 =A0 Michal Hocko (MM) =A0 =A0 =A0 =A0 Dan Williams (MM) =A0 =A0 =A0 =A0 Alexei Starovoitov (BPF) =A0 =A0 =A0 =A0 Daniel Borkmann (BPF)