From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Luke Yang <luke.adi@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH] nommu page refcount bug fixing
Date: Thu, 30 Mar 2006 19:07:17 +1000 [thread overview]
Message-ID: <442B9FC5.4040409@yahoo.com.au> (raw)
In-Reply-To: <489ecd0c0603300100o7e9293b4mbde4340b0129e5d5@mail.gmail.com>
Luke Yang wrote:
>>>NOMMU special-casing in page refcounting. As a temporary fix, what I
>>>think should happen is simply for all slab allocations to ask for
>>>__GFP_COMP pages.
>>>
>>>Could you check that fixes your problem?
>>
>> It works. What's your plan to modify nommu mm? I would like to
>>help. And I am also interested in implementing the "non-power-of-2"
>>allocator in 2.6.
>>
I'll get it up to date and send it over to you, offline. It
would be great if you could help.
>> New patch:
>
Acked-by: Nick Piggin <npiggin@suse.de>
I'll write a changelog for you:
***
The earlier patch to consolidate mmu and nommu page allocation
and refcounting by using compound pages for nommu allocations
had a bug: kmalloc slabs who's pages were initially allocated
by a non-__GFP_COMP allocator could be passed into mm/nommu.c
kmalloc allocations which really wanted __GFP_COMP underlying
pages.
Fix that by having nommu pass __GFP_COMP to all higher order
slab allocations
***
Sound OK? Can you do it next time? ;)
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2006-03-30 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 3:05 [PATCH] nommu page refcount bug fixing Luke Yang
2006-03-30 3:22 ` Nick Piggin
2006-03-30 8:56 ` Luke Yang
2006-03-30 9:00 ` Luke Yang
2006-03-30 9:07 ` Nick Piggin [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=442B9FC5.4040409@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.adi@gmail.com \
--cc=npiggin@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.