All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rafael Aquini <aquini@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, hca@linux.ibm.com,
	kirill.shutemov@linux.intel.com, mm-commits@vger.kernel.org,
	vbabka@suse.cz, vdavydov.dev@gmail.com, yuzhao@google.com
Subject: Re: + mm-mark-idle-page-tracking-as-broken.patch added to -mm tree
Date: Thu, 17 Jun 2021 11:54:31 -0400	[thread overview]
Message-ID: <YMtwN7nIvw/yl0gW@optiplex-fbsd> (raw)
In-Reply-To: <YMtsLVyQsrROCeiG@casper.infradead.org>

On Thu, Jun 17, 2021 at 04:37:17PM +0100, Matthew Wilcox wrote:
> On Wed, Jun 16, 2021 at 06:29:19PM -0400, Rafael Aquini wrote:
> > > In discussion with other MM developers around how idle page tracking
> > > should be fixed for transparent huge pages, several expressed the opinion
> > > that it should be removed as it is inefficient at accomplishing the job
> > > that it is supposed to, and we have better mechanisms (eg uffd) for
> > > accomplishing the same goals these days.
> > 
> > I didn't follow the aforementioned discussion, so it would be nice to
> > have a little bit more detailed explanation on both points raised here
> > (issues with THP and innefficiency). There are some Red Hat customers
> > and partners that do rely on the feature, thus the interest. Thanks.
> 
> It would be nice if you asked this on the original thread (which you're
> cc'd on) instead of starting a new thread.

Sorry about that, but for some weird reason only Andrew's email made its way
into my inbox.



> > > Mark the feature as BROKEN for now and we can remove it entirely in a few
> > > months if nobody complains.  It is not enabled by Android, ChromeOS,
> > > Debian, Fedora or SUSE.  Red Hat enabled it with RHEL-8.1 and UEK followed
> > > suit, but I have been unable to find why RHEL enabled it.
> > 
> > minor nit on the RHEL mention: CONFIG_IDLE_PAGE_TRACKING is enabled since 8.0
> > for RHEL-8, and 7.7 for RHEL-7.
> 
> Red Hat makes it incredibly hard to find out what changed when.
> You can't then whine about us not understanding what you're doing,
> when you're going out of your way to obfuscate what you do.
>

Not whining about it, just pointing out the fixup. That's part
of the review process, isn't it? There's no need to whine back at it.



  reply	other threads:[~2021-06-17 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15  2:05 + mm-mark-idle-page-tracking-as-broken.patch added to -mm tree akpm
2021-06-16 22:29 ` Rafael Aquini
2021-06-17 15:37   ` Matthew Wilcox
2021-06-17 15:54     ` Rafael Aquini [this message]
2021-06-17 16:01       ` Matthew Wilcox

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=YMtwN7nIvw/yl0gW@optiplex-fbsd \
    --to=aquini@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hca@linux.ibm.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=vbabka@suse.cz \
    --cc=vdavydov.dev@gmail.com \
    --cc=willy@infradead.org \
    --cc=yuzhao@google.com \
    /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.