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=-3.8 required=3.0 tests=BAYES_00, 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 ED875C433EF for ; Wed, 15 Sep 2021 17:42:36 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 6C7B361101 for ; Wed, 15 Sep 2021 17:42:36 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 6C7B361101 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mit.edu Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id CA0816B0071; Wed, 15 Sep 2021 13:42:35 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id C5062900002; Wed, 15 Sep 2021 13:42:35 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B3F556B0073; Wed, 15 Sep 2021 13:42:35 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0136.hostedemail.com [216.40.44.136]) by kanga.kvack.org (Postfix) with ESMTP id A577D6B0071 for ; Wed, 15 Sep 2021 13:42:35 -0400 (EDT) Received: from smtpin39.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 581F13E579 for ; Wed, 15 Sep 2021 17:42:35 +0000 (UTC) X-FDA: 78590527470.39.88EFD8A Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by imf20.hostedemail.com (Postfix) with ESMTP id 0D3F3D0000B5 for ; Wed, 15 Sep 2021 17:42:34 +0000 (UTC) Received: from cwcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 18FHgO2e004544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 15 Sep 2021 13:42:25 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 360D215C3424; Wed, 15 Sep 2021 13:42:24 -0400 (EDT) Date: Wed, 15 Sep 2021 13:42:24 -0400 From: "Theodore Ts'o" To: Johannes Weiner Cc: Kent Overstreet , Matthew Wilcox , Linus Torvalds , linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Morton , "Darrick J. Wong" , Christoph Hellwig , David Howells , ksummit@lists.linux.dev Subject: [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic? Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 0D3F3D0000B5 X-Stat-Signature: 7r8fsn18rykco4etywxtbu57et5kbwc4 Authentication-Results: imf20.hostedemail.com; dkim=none; spf=none (imf20.hostedemail.com: domain of tytso@mit.edu has no SPF policy when checking 18.9.28.11) smtp.mailfrom=tytso@mit.edu; dmarc=none X-HE-Tag: 1631727754-448296 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: Back when we could fit all or most of the Maintainers plus interested developers in a single room, the question of how to make forward progress on something like Folios. These days, all of the interested parties wouldn't fit in a single room, which is why Maintainers summit focuses only on development process issues. However, this means that when we need to make a call about what needs to happen before Folios can be merged, we don't seem to have a good way to make that happen. And being a file system developer who is eagerly looking forward to what Folios will enable, I'm a bit biased in terms of wanting to see how we can break the logjam and move forward. So.... I have a proposal. We could potentially schedule a Wither Folios LPC BOF during one of the time slots on Friday when the Maintainers Summit is taking place, and we arrange to have all of the Maintainers switch over to the LPC BOF room. If enough of the various stakeholders for Folios are going to be attending LPC or Maintainer's Summit, and folks (especially Linus, who ultiamtely needs to make the final decision), this is something we could do. Would this be helpful? (Or Linus could pull either the folio or pageset branch, and make this proposal obsolete, which would be great. :-) - Ted