From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Folio tree for next
Date: Wed, 21 Jul 2021 03:46:52 +0100 [thread overview]
Message-ID: <YPeKnIpd+EAU4SZP@casper.infradead.org> (raw)
In-Reply-To: <20210720192927.98ee7809717b9cc28fa95bb6@linux-foundation.org>
On Tue, Jul 20, 2021 at 07:29:27PM -0700, Andrew Morton wrote:
> On Wed, 21 Jul 2021 12:21:02 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi Matthew,
> >
> > On Tue, 20 Jul 2021 03:55:44 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> > >
> > > I think conceptually, the folio for-next tree is part of mmotm for this
> > > cycle. I would have asked Andrew to carry these patches, but there are
> > > people (eg Dave Howells) who want to develop against them. And that's
> > > hard to do with patches that are in mmotm.
> > >
> > > So if Andrew bases mmotm on the folio tree for this cycle, does that
> > > make sense?
> >
> > Sure. I will have a little pain the first day it appears, but it
> > should be OK after that. I am on leave starting Saturday, so if you
> > could get me a tree without the mmotm patches for tomorrow that would
> > be good.
>
> Sure, let's go that way. Linus wasn't terribly enthusiastic about the
> folio patches and I can't claim to be overwhelmed by their value/churn
> ratio (but many MM developers are OK with it all, and that
> counts). Doing it this way retains options...
I'm happy to take these three patches through my tree if it makes life
easier (and it does resolve the majority of the pain):
mm, memcg: add mem_cgroup_disabled checks in vmpressure and swap-related functions
mm, memcg: inline mem_cgroup_{charge/uncharge} to improve disabled memcg config
mm, memcg: inline swap-related functions to improve disabled memcg config
Up to you, really.
next prev parent reply other threads:[~2021-07-21 2:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 3:18 Folio tree for next Matthew Wilcox
2021-07-19 3:57 ` Andrew Morton
2021-07-19 23:40 ` Stephen Rothwell
2021-07-19 23:51 ` Stephen Rothwell
2021-07-20 2:55 ` Matthew Wilcox
2021-07-21 2:21 ` Stephen Rothwell
2021-07-21 2:29 ` Andrew Morton
2021-07-21 2:46 ` Matthew Wilcox [this message]
2021-07-21 3:22 ` Andrew Morton
2021-07-21 3:22 ` Matthew Wilcox
2021-07-21 5:04 ` Stephen Rothwell
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=YPeKnIpd+EAU4SZP@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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.