All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	David Howells <dhowells@redhat.com>,
	ksummit@lists.linux.dev
Subject: [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic?
Date: Wed, 15 Sep 2021 13:42:24 -0400	[thread overview]
Message-ID: <YUIwgGzBqX6ZiGgk@mit.edu> (raw)

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

             reply	other threads:[~2021-09-15 17:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 17:42 Theodore Ts'o [this message]
2021-09-15 18:03 ` [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic? James Bottomley
2021-09-15 18:03   ` James Bottomley
2021-09-15 18:20   ` Theodore Ts'o
2021-09-15 18:41     ` Chris Mason
2021-09-15 19:15       ` James Bottomley
2021-09-15 19:15         ` James Bottomley
2021-09-15 20:48         ` Theodore Ts'o
2021-09-16 14:55           ` Kent Overstreet
2021-09-16 13:51         ` David Howells
2021-09-16 16:46         ` Chris Mason
2021-09-16 17:11           ` James Bottomley
2021-09-16 17:11             ` James Bottomley
2021-09-16 19:15             ` Theodore Ts'o
2021-09-16 19:26               ` Andrew Morton
2021-09-16 20:16               ` Kent Overstreet
2021-09-17  1:42                 ` Theodore Ts'o
2021-09-17  4:58                   ` Kent Overstreet
2021-09-16 20:38             ` Chris Mason
2021-09-16 21:00               ` Konstantin Ryabitsev
2021-09-17 11:14                 ` James Bottomley
2021-09-17 11:14                   ` James Bottomley
2021-09-17 12:36                   ` Konstantin Ryabitsev
2021-09-17 13:00                     ` James Bottomley
2021-09-17 13:00                       ` James Bottomley
2021-09-17 14:36                       ` Chris Mason
2021-09-16 17:15           ` Kent Overstreet
2021-09-16 22:27             ` Chris Mason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YUIwgGzBqX6ZiGgk@mit.edu \
    --to=tytso@mit.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=hch@infradead.org \
    --cc=kent.overstreet@gmail.com \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.