All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Move slab objects to the end of the real allocation
Date: Mon, 22 Sep 2003 22:53:36 +0200	[thread overview]
Message-ID: <3F6F6150.10808@colorfullife.com> (raw)
In-Reply-To: <200309222240.01023.arnd@arndb.de>

Arnd Bergmann wrote:

>On Monday 22 September 2003 18:31, Manfred Spraul wrote:
>  
>
>>Right now there are too many patches in Andrew's tree, I'll wait until
>>everything settled down a bit, then I'll resent the cache line size as a
>>one-line patch. Do you want to implement CONFIG_DEBUG_PAGEALLOC
>>immediately? If yes, then I can send you the oneliner immediately.
>>Nothing except CONFIG_DEBUG_PAGEALLOC is affected by the bug.
>>    
>>
>
>Thanks for the explanation. I didn't realize that the code only applies
>to i386. I'm not trying to implement CONFIG_DEBUG_PAGEALLOC currently,
>but I'll put it on my list of things to do. Do I need to do anything
>beyond adding a working kernel_map_pages() and raising the 128 byte limit
>in kmem_cache_create to max(128,L1_CACHE_BYTES)?
>  
>
I'm not aware of any other restrictions, but I think s390 would be the 
first arch beyond i386 that supports DEBUG_PAGEALLOC, so beware. One 
important point is that kernel_map_pages() can be called from irq 
context - I'm not sure if all archs can support that.

--
    Manfred


  reply	other threads:[~2003-09-22 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 15:33 [PATCH] Move slab objects to the end of the real allocation Arnd Bergmann
2003-09-22 16:31 ` Manfred Spraul
2003-09-22 20:40   ` Arnd Bergmann
2003-09-22 20:53     ` Manfred Spraul [this message]
2003-09-23  2:52       ` Anton Blanchard

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=3F6F6150.10808@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.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 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.