LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Kent Overstreet <kent.overstreet@gmail.com>,
	"Matthew Wilcox" <willy@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@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" <ksummit@lists.linux.dev>
Subject: Re: [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic?
Date: Wed, 15 Sep 2021 18:41:34 +0000	[thread overview]
Message-ID: <17242A0C-3613-41BB-84E4-2617A182216E@fb.com> (raw)
In-Reply-To: <YUI5bk/94yHPZIqJ@mit.edu>


> On Sep 15, 2021, at 2:20 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> 
> On Wed, Sep 15, 2021 at 02:03:46PM -0400, James Bottomley wrote:
>> On Wed, 2021-09-15 at 13:42 -0400, Theodore Ts'o wrote:
>> [...]
>>> Would this be helpful?  (Or Linus could pull either the folio or
>>> pageset branch, and make this proposal obsolete, which would be
>>> great.  :-)
>> 
>> This is a technical rather than process issue isn't it?  You don't have
>> enough technical people at the Maintainer summit to help meaningfully. 
>> The ideal location, of course, was LSF/MM which is now not happening.
>> 
>> However, we did offer the Plumbers BBB infrastructure to willy for a MM
>> gathering which could be expanded to include this.
> 
> Well, that's why I was suggesting doing this as a LPC BOF, and using
> an LPC BOF session on Friday --- I'm very much aware we don't have the
> right tehcnical people at the Maintainer Summit.
> 
> It's not clear we will have enough MM folks at the LPC, and I agree
> LSF/MM would be a better venue --- but as you say, it's not happening.
> We could also use the BBB infrastructure after the LPC as well, if we
> can't get everyone lined up and available on short notice.  There are
> a lot of different possibilities; I'm for anything where all of the
> stakeholders agree will work, so we can make forward progress.

I think the two different questions are:

* What work is left for merging folios?

* What process should we use to make the overall development of folio sized changes more predictable and rewarding for everyone involved?

-chris

  reply	other threads:[~2021-09-15 18:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 17:42 Theodore Ts'o
2021-09-15 18:03 ` James Bottomley
2021-09-15 18:20   ` Theodore Ts'o
2021-09-15 18:41     ` Chris Mason [this message]
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 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 12:36                   ` Konstantin Ryabitsev
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=17242A0C-3613-41BB-84E4-2617A182216E@fb.com \
    --to=clm@fb.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --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=tytso@mit.edu \
    --cc=willy@infradead.org \
    --subject='Re: [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).