linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 5/5] powerpc: Don't use SLAB/SLUB for PTE pages
Date: Wed, 09 May 2007 07:17:30 +1000	[thread overview]
Message-ID: <1178659050.14928.78.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0705082035430.17227@blonde.wat.veritas.com>

On Tue, 2007-05-08 at 20:50 +0100, Hugh Dickins wrote:
> On Tue, 8 May 2007, Benjamin Herrenschmidt wrote:
> > From: Hugh Dickins <hugh@veritas.com>
> > 
> > The SLUB allocator relies on struct page fields first_page and slab,
> > overwritten by ptl when SPLIT_PTLOCK: so the SLUB allocator cannot then
> > be used for the lowest level of pagetable pages.  This was obstructing
> > SLUB on PowerPC, which uses kmem_caches for its pagetables.  So convert
> > its pte level to use normal gfp pages (whereas pmd, pud and 64k-page pgd
> > want partpages, so continue to use kmem_caches for pmd, pud and pgd).
> > 
> > Signed-off-by: Hugh Dickins <hugh@veritas.com>
> > Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > ---
> 
> Looks and runs fine for me (though would have seemed nicer to use
> __GFP_ZERO than clear_page - or does that subvert your fast zeroing?).

Nah, you are right, I'll respin. Forgot about __GFP_ZERO. It just called
clear_highpage on the returned pages right ? This is the same as calling
clear_page from my code.

> But you also need to undo the ARCH_USES_SLAB_PAGE_STRUCT from
> arch/powerpc/Kconfig now that's gone into Linus' tree: patch
> I added in testing below (either append to this one or add a 6/5).

I was thinking about adding a new patch.

> For some people that interim disablement was working, for other
> people it wasn't: mysterious, and the sooner it's got rid of the
> better.  I'm sorry to find that oldconfig doesn't actually offer
> the SLAB or SLUB menu (to me anyway) when moving from SLUB disabled
> to SLUB enabled: so again, the sooner we get rid of that interim
> disablement the better for SLUB exposure.

Ok. I'll post a new patch along with the final serie after I've done some
testing later today.

Cheers,
Ben.

  reply	other threads:[~2007-05-08 21:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08  6:27 [PATCH 0/5] This is my pending series for 2.6.22 Benjamin Herrenschmidt
2007-05-08  6:27 ` [PATCH 2/5] powerpc: Introduce address space "slices" Benjamin Herrenschmidt
2007-05-08  6:27 ` [PATCH 1/5] powerpc: Small fixes & cleanups in segment page size demotion Benjamin Herrenschmidt
2007-05-08  6:27 ` [PATCH 3/5] powerpc: Add ability to 4K kernel to hash in 64K pages Benjamin Herrenschmidt
2007-05-08  6:27 ` [PATCH 4/5] powerpc: spufs support for 64K LS mappings on 4K kernels Benjamin Herrenschmidt
2007-05-08  6:27 ` [PATCH 5/5] powerpc: Don't use SLAB/SLUB for PTE pages Benjamin Herrenschmidt
2007-05-08 19:50   ` Hugh Dickins
2007-05-08 21:17     ` Benjamin Herrenschmidt [this message]
2007-05-09  4:38   ` Benjamin Herrenschmidt

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=1178659050.14928.78.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=hugh@veritas.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).