All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Zhao <yuzhao@google.com>
To: David Hildenbrand <david@redhat.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
	akpm@linuxfoundation.org, Linux-MM <linux-mm@kvack.org>,
	 Heiko Carstens <hca@linux.ibm.com>,
	Rafael Aquini <aquini@redhat.com>,
	 Vladimir Davydov <vdavydov.dev@gmail.com>,
	 "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	 Donald Dutile <ddutile@redhat.com>,
	Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] mm: Mark idle page tracking as BROKEN
Date: Wed, 16 Jun 2021 13:23:22 -0600	[thread overview]
Message-ID: <CAOUHufbdF=LBFZbJuJg+P73uoaR1jrC4zXSCsivT6F6puaDYFg@mail.gmail.com> (raw)
In-Reply-To: <7b35885b-1413-5e08-3930-c8c4b66bcfe7@redhat.com>

On Wed, Jun 16, 2021 at 2:43 AM David Hildenbrand <david@redhat.com> wrote:
>
> On 16.06.21 10:36, Vlastimil Babka wrote:
> > On 6/16/21 8:22 AM, Yu Zhao wrote:
> >> On Tue, Jun 15, 2021 at 8:55 PM Matthew Wilcox <willy@infradead.org> wrote:
> >>>
> >>>
> >>> I don't know.  I asked the others on the call and the answer I got was
> >>> essentially "Just delete it".
> >>>
> >>> I'm kind of hoping the others speak up.
> >>
> >> I listed a couple of things when acking this patch. Being broken is
> >> not a problem as long as there are users who care about it. What made
> >> me think such users may not exist is that nobody ever complained about
> >> those things until we stumbled on them -- I'm not insisting on
> >> deleting this feature, just clarifying why I thought so.
> >
> > Similar feelings here. On the call it looked like the feature was abandoned by
> > its creators, and it wasn't clear if the distros that had it enabled did so due
> > to reasons that still apply for future versions. Sending the proposal and
> > getting a feedback that there are users is one of the expected valid outcomes.
>
> For us (RH) it will be very interesting to know the exact things that
> are "suboptimal" (I'm avoiding the terminology "broken" here), so we can
> actually evaluate if this might affect customers and might be worth
> "improving".

I consider the examples I gave in my first email breakages -- others
broke/break the idle page tracking -- and I think it's safe to assume
they will continue to happen.

If you are really looking for improvements, the page compaction has
always been a good example. For the idle page tracking, with physical
memory as little as 4GB, it needs to go thru one million PFNs, no
matter how many compound or buddy pages there are. For THPs, it will
try to get_page_unless_zero() on tail pages, which always fails. This
is why we discussed it in the meeting.

What can't be improved is the memory locality of PFNs. They are not
grouped by memcgs or processes. Two PFNs next to each other can be
from two processes with two sets of five-level page tables. The cache
misses simply outweigh any potential benefits one might get from this
feature, speaking as one of the customers.


  reply	other threads:[~2021-06-16 19:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  0:07 [PATCH] mm: Mark idle page tracking as BROKEN Matthew Wilcox (Oracle)
2021-06-12  3:14 ` Yu Zhao
2021-06-14 11:08 ` Kirill A. Shutemov
2021-06-14 13:49 ` SeongJae Park
2021-06-15  2:04   ` Andrew Morton
2021-06-15  6:40     ` SeongJae Park
2021-06-15  7:41 ` David Hildenbrand
2021-06-16  2:55   ` Matthew Wilcox
2021-06-16  6:22     ` Yu Zhao
2021-06-16  8:36       ` Vlastimil Babka
2021-06-16  8:43         ` David Hildenbrand
2021-06-16 19:23           ` Yu Zhao [this message]
2021-06-18 12:48             ` David Hildenbrand

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='CAOUHufbdF=LBFZbJuJg+P73uoaR1jrC4zXSCsivT6F6puaDYFg@mail.gmail.com' \
    --to=yuzhao@google.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linuxfoundation.org \
    --cc=aquini@redhat.com \
    --cc=david@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=hca@linux.ibm.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    --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 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.