All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	akpm@osdl.org, linux-mm@kvack.org,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	mpm@selenic.com, Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [RFC] Extract kmalloc.h and slob.h from slab.h
Date: Thu, 30 Nov 2006 14:44:50 +1100	[thread overview]
Message-ID: <456E53B2.9020701@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0611291937560.19557@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Thu, 30 Nov 2006, Nick Piggin wrote:
> 
> 
>>I don't see the problem with slab/slob. It is not the nicest code, but it
>>isn't unreadable. We do something very similar with nommu, for (perhaps
>>not the best!) example.
> 
> 
> I need some order in there to add another type of slab allocator without 
> getting into an umaintainable mess.

OK, slab_defs.h and slob_defs.h would work, wouldn't it? That seems to be
the standard pattern used when alternatives become too numerous / complex
to be in a single file.

>>But kmalloc seems like one thing that could be split nicely. It would
>>allow you to get rid of asm/page.h and asm/cache.h from slab.h
>>(converting callers would be a bigger job).
> 
> 
> What callers would need to be converted?

When you remove kmalloc.h from slab.h? I guess anyone that includes
slab.h in order to get kmalloc.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-11-30  3:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28  6:33 [RFC] Extract kmalloc.h and slob.h from slab.h Christoph Lameter
2006-11-28  8:00 ` Pekka Enberg
2006-11-28 18:05   ` Christoph Lameter
2006-11-28 19:07     ` Pekka J Enberg
2006-11-28 19:11       ` Christoph Lameter
2006-11-28 19:19         ` Pekka J Enberg
2006-11-28 19:24           ` Pekka Enberg
2006-11-28 19:27             ` Christoph Lameter
2006-11-28 19:25           ` Christoph Lameter
2006-11-28 19:32             ` Pekka Enberg
2006-11-28 19:53               ` Christoph Lameter
2006-11-29  0:30               ` Christoph Lameter
2006-11-29  7:08                 ` Pekka Enberg
2006-11-29 19:18                   ` Christoph Lameter
2006-11-29  8:26 ` Christoph Hellwig
2006-11-29  8:38   ` Nick Piggin
2006-11-29 19:24     ` Christoph Lameter
2006-11-30  1:58       ` Nick Piggin
2006-11-30  2:43         ` Christoph Lameter
2006-11-30  3:04           ` Nick Piggin
2006-11-30  3:39             ` Christoph Lameter
2006-11-30  3:44               ` Nick Piggin [this message]
2006-11-30  3:50                 ` Christoph Lameter
2006-11-30  4:18                   ` Nick Piggin
2006-11-30  4:28                     ` Christoph Lameter
2006-11-30  5:01                       ` Nick Piggin
2006-11-30  7:12         ` Pekka Enberg

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=456E53B2.9020701@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=manfred@colorfullife.com \
    --cc=mpm@selenic.com \
    --cc=penberg@cs.helsinki.fi \
    /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.