From: Michal Hocko <mhocko@suse.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC] memcg: Convert mc_target.page to mc_target.folio
Date: Fri, 18 Mar 2022 10:12:37 +0100 [thread overview]
Message-ID: <YjRNBdEENrNNrUNe@dhcp22.suse.cz> (raw)
In-Reply-To: <YjQBRx1+Rq7CYC4M@casper.infradead.org>
On Fri 18-03-22 03:49:27, Matthew Wilcox wrote:
> On Thu, Mar 17, 2022 at 12:58:46PM +0100, Michal Hocko wrote:
> > On Wed 16-03-22 20:31:30, Matthew Wilcox wrote:
> > > This is a fairly mechanical change to convert mc_target.page to
> > > mc_target.folio. This is a prerequisite for converting
> > > find_get_incore_page() to find_get_incore_folio(). But I'm not
> > > convinced it's right, and I'm not convinced the existing code is
> > > quite right either.
> > >
> > > In particular, the code in hunk @@ -6036,28 +6041,26 @@ needs
> > > careful review. There are also assumptions in here that a memory
> > > allocation is never larger than a PMD, which is true today, but I've
> > > been asked about larger allocations.
> >
> > Could you be more specific about those usecases? Are they really
> > interested in supporting larger pages for the memcg migration which is
> > v1 only feature? Or you are interested merely to have the code more
> > generic?
>
> Ah! I didn't realise memcg migration was a v1-only feature. I think
> that makes all of the questions much less interesting. I've done some
> more reading, and it seems like all of this is "best effort", so it
> doesn't really matter if some folios get skipped.
Yes.
[...]
> That makes sense. I think the case that's currently mishandled is a
> THP in tmpfs which is misaligned when mapped to userspace. It's
> skipped, even if the entire THP is mapped. But maybe that simply
> doesn't matter.
>
> I suppose the question is: Do we care if mappings of files are not
> migrated to the new memcg? I'm getting a sense that the answer is "no",
> and if we actually ended up skipping all file mappings, it wouldn't
> matter.
Yes, I wouldn't lose sleep over that. You are not introducing a new
regression. The feature is mostly deprecated (along with the whole v1)
so we tend to prefer bug-to-bug compatibility rather than making the
code more complex to solve a theoretical problem (or at least a problem
that nobody is complaining about).
Thanks!
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2022-03-18 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 20:31 Matthew Wilcox
2022-03-17 11:58 ` Michal Hocko
2022-03-18 3:49 ` Matthew Wilcox
2022-03-18 9:12 ` Michal Hocko [this message]
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=YjRNBdEENrNNrUNe@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.com \
--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