mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <ak@suse.de>,
	William Lee Irwin III <wli@holomorphy.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Christoph Lameter <clameter@sgi.com>,
	David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: slub-i386-support.patch
Date: Fri, 11 May 2007 10:27:39 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705111026200.25712@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070511004200.6d30152e.akpm@linux-foundation.org>

On Fri, 11 May 2007, Andrew Morton wrote:
> On Fri, 11 May 2007 10:29:30 +0200 Andi Kleen <ak@suse.de> wrote:
> 
> > > I'm guessing (haven't rechecked source) that the cpu_idle() call comes
> > > about because the top level pgd of a process gets freed very late in
> > > its exit, and after a great flurry of processes have just exited,
> > > perhaps there was nothing to free up the accumulation.  Though
> > > it still strikes me as an odd place to do it.
> > 
> > I always found it odd and probably the wrong place too.
> 
> so... what's the bottom line here, guys?  Should we change that patch?

The bottom line... I can see why you're asking for that ;)

I'd say delete the change to arch/i386/kernel/smp.c - contrary to
what Christoph says, no other arch buries a check_pgt_cache() call
in flush_tlb_mm(), that just seems to be a thinko: i386 has the usual
call to it from tlb_finish_mmu() - _that_ is the one which he and
David were talking about.

I'm just worried that there might somewhere be a call to flush_tlb_mm()
which would now be surprised to be freeing pages: almost certainly not,
but why raise that concern?  It's just not flush_tlb_mm()'s business.

The cpu_idle() call should stay for now: we're agreed that it's odd,
but there's plenty of precedent for it, and it's easier to imagine it
serves a real purpose, and shouldn't be removed without replacement.

Bill raised a real concern about unnecessary PAE pgd memory usage,
but let's get the patch into -rc1 to enable the wider SLUB testing,
before coming back to fix that up.  His micro-optimizations can wait.

IMHO
Hugh

      parent reply	other threads:[~2007-05-11  9:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 20:03 slub-i386-support.patch Hugh Dickins
2007-05-10 20:17 ` slub-i386-support.patch Andrew Morton
2007-05-10 20:31   ` slub-i386-support.patch Christoph Lameter
2007-05-10 20:50     ` slub-i386-support.patch David Miller
2007-05-10 20:31 ` slub-i386-support.patch William Lee Irwin III
2007-05-10 20:35   ` slub-i386-support.patch Christoph Lameter
2007-05-10 21:09     ` slub-i386-support.patch William Lee Irwin III
2007-05-10 21:28       ` slub-i386-support.patch Jeremy Fitzhardinge
2007-05-10 23:35         ` slub-i386-support.patch William Lee Irwin III
2007-05-10 21:22     ` slub-i386-support.patch Jeremy Fitzhardinge
2007-05-10 23:14   ` slub-i386-support.patch Hugh Dickins
2007-05-11  0:07     ` slub-i386-support.patch William Lee Irwin III
2007-05-11  1:08       ` slub-i386-support.patch William Lee Irwin III
2007-05-11  5:09         ` slub-i386-support.patch Christoph Lameter
2007-05-11  7:43           ` slub-i386-support.patch William Lee Irwin III
2007-05-11  1:42       ` slub-i386-support.patch William Lee Irwin III
2007-05-11  8:29     ` slub-i386-support.patch Andi Kleen
2007-05-11  7:42       ` slub-i386-support.patch Andrew Morton
2007-05-11  7:54         ` slub-i386-support.patch William Lee Irwin III
2007-05-11 16:15           ` slub-i386-support.patch Christoph Lameter
2007-05-11 20:47             ` slub-i386-support.patch William Lee Irwin III
2007-05-11  9:27         ` Hugh Dickins [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=Pine.LNX.4.64.0705111026200.25712@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®