public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: clameter@sgi.com
Cc: akpm@linux-foundation.org, hugh@veritas.com,
	torvalds@linux-foundation.org, ak@suse.de, wli@holomorphy.com,
	linux-kernel@vger.kernel.org
Subject: Re: slub-i386-support.patch
Date: Thu, 10 May 2007 13:50:32 -0700 (PDT)	[thread overview]
Message-ID: <20070510.135032.68041531.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0705101328110.11759@schroedinger.engr.sgi.com>

From: Christoph Lameter <clameter@sgi.com>
Date: Thu, 10 May 2007 13:31:21 -0700 (PDT)

> On Thu, 10 May 2007, Andrew Morton wrote:
> 
> > > Though when I look at the patchset (copied below), I do wonder why
> > > it puts a quicklist_trim() into i386's cpu_idle() and flush_tlb_mm():
> > > neither is where I'd expect us to be secretly freeing pages.  Ah,
> > > several arches do it in cpu_idle(): how odd, oh well.
> > 
> > Christoph, could you please check that this is justified?
> 
> This has been that way for years for ia64 and sparc64. quicklist page 
> freeing needs to be synced with the tlb flushing since page table pages 
> may be flushed with the pages gathered in the tlb_mm struct. Dave Miller 
> set this up initially as far as I can tell. He could probably give more 
> details on why this was done historically.
> 
> ccing Dave.

I think it was just a convenient place to get it trimmed.

There could be some implications for platforms using virtual
page tables like IA64 et al. (sparc64 is no longer using
virtual page table mappings for TLB misses although it used to).

But I can't figure out a reason in that area for this stuff
either.


  reply	other threads:[~2007-05-10 20:50 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     ` David Miller [this message]
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         ` slub-i386-support.patch Hugh Dickins

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=20070510.135032.68041531.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=hugh@veritas.com \
    --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