public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andi Kleen <ak@suse.de>, Christoph Lameter <clameter@sgi.com>,
	William Lee Irwin III <wli@holomorphy.com>,
	linux-kernel@vger.kernel.org
Subject: Re: slub-i386-support.patch
Date: Thu, 10 May 2007 13:17:24 -0700	[thread overview]
Message-ID: <20070510131724.150e1e99.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705102028550.25681@blonde.wat.veritas.com>

On Thu, 10 May 2007 21:03:39 +0100 (BST)
Hugh Dickins <hugh@veritas.com> wrote:

> Just want to report that I've been running SLUB on i386, both in -mm
> and with slub-i386-support.patch applied to 2.6.21-git, and observed
> no problems with it.  I'm anxious that it (or an equivalent) go into
> 2.6.22-rc1, i386 being now the last ARCH_USES_SLAB_PAGE_STRUCT holdout.
> 
> In the frenzy over PowerPC, maybe Linus overlooked that i386
> was still not supporting SLUB; and I fear that once people get
> "# CONFIG_SLUB is not set" into their .config, they're less likely to
> switch over to testing CONFIG_SLUB=y - I remain anxious that it see
> as much testing as possible (but under EXPERIMENTAL for 2.6.22, yes).

ok..

> 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?

  reply	other threads:[~2007-05-10 20:17 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 ` Andrew Morton [this message]
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         ` 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=20070510131724.150e1e99.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ak@suse.de \
    --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