From: Rob Landley <rob@landley.net>
Organization: Boundaries Unlimited
To: Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH 2/2] slob: introduce the SLOB allocator
Date: Tue, 1 Nov 2005 14:51:54 -0600
User-Agent: KMail/1.8
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
References: <3.494767362@selenic.com>
In-Reply-To: <3.494767362@selenic.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200511011451.55362.rob@landley.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 981
Lines: 21

On Tuesday 01 November 2005 12:33, Matt Mackall wrote:
> SLOB is a traditional K&R/UNIX allocator with a SLAB emulation layer,
> similar to the original Linux kmalloc allocator that SLAB replaced.
> It's signicantly smaller code and is more memory efficient. But like
> all similar allocators, it scales poorly and suffers from
> fragmentation more than SLAB, so it's only appropriate for small
> systems.

Just to clarify: define "small".  My current laptop has half a gigabyte of 
ram.  (Yeah, I broke down and bought a real machine, and even kept a World of 
Warcraft partition this time...)

Does small mean "this is better for laptops with < 4gig"?  In which case, 
possibly this should be tied to CONFIG_HIGHMEM or some such?

Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/