linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Christoph Lameter <cl@linux.com>,
	linux-arch@vger.kernel.org, linux-ia64@vger.kernel.org,
	linux-mm@kvack.org, linux-sh@vger.kernel.org
Subject: Re: [RFC PATCH] mm: remove quicklist page table caches
Date: Thu, 11 Jul 2019 20:30:00 +1000	[thread overview]
Message-ID: <1562840680.snxfuzmtxv.astroid@bobo.none> (raw)
In-Reply-To: <20190711082539.GC29483@dhcp22.suse.cz>

Michal Hocko's on July 11, 2019 6:25 pm:
> On Thu 11-07-19 13:03:39, Nicholas Piggin wrote:
>> Remove page table allocator "quicklists". These have been around for a
>> long time, but have not got much traction in the last decade and are
>> only used on ia64 and sh architectures.
>> 
>> The numbers in the initial commit look interesting but probably don't
>> apply anymore. If anybody wants to resurrect this it's in the git
>> history, but it's unhelpful to have this code and divergent allocator
>> behaviour for minor archs.
>> 
>> Also it might be better to instead make more general improvements to
>> page allocator if this is still so slow.
> 
> Agreed. And if that is not possible for whatever reason then we have a
> proper justification for the revert at least.
> 
> Acked-by: Michal Hocko <mhocko@suse.com>

Thanks. If it's agreed with ia64 and sh maintainers, I can send
individual patches through their trees, then the removal patch
will be functionally a nop that can be easily pushed through.

Thanks,
Nick


  reply	other threads:[~2019-07-11 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11  3:03 Nicholas Piggin
2019-07-11  7:54 ` Christopher Lameter
2019-07-11  8:23   ` Thomas Gleixner
2019-07-11  9:24   ` Nicholas Piggin
2019-07-11  8:25 ` Michal Hocko
2019-07-11 10:30   ` Nicholas Piggin [this message]
2019-07-11 10:36 ` Mike Rapoport

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=1562840680.snxfuzmtxv.astroid@bobo.none \
    --to=npiggin@gmail.com \
    --cc=cl@linux.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=mhocko@kernel.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