From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.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: Tue, 20 Jul 2021 20:22:02 -0700 [thread overview]
Message-ID: <20210720202202.dfd4d9c3490e51e35cf1455e@linux-foundation.org> (raw)
In-Reply-To: <YPeKnIpd+EAU4SZP@casper.infradead.org>
On Wed, 21 Jul 2021 03:46:52 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> > 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
They're rather unimportant, can be deferred.
I'll probably move these to the post-linux-next queue, but let's just
do it and see how it goes.
next prev parent reply other threads:[~2021-07-21 3:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 3:18 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
2021-07-21 3:22 ` Andrew Morton [this message]
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=20210720202202.dfd4d9c3490e51e35cf1455e@linux-foundation.org \
--to=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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox