From: Rob Landley <rob@landley.net>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] slob: introduce the SLOB allocator
Date: Tue, 1 Nov 2005 14:51:54 -0600 [thread overview]
Message-ID: <200511011451.55362.rob@landley.net> (raw)
In-Reply-To: <3.494767362@selenic.com>
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
next prev parent reply other threads:[~2005-11-01 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 18:33 [PATCH 1/2] slob: move kstrdup to lib/string.c Matt Mackall
2005-11-01 18:33 ` [PATCH 2/2] slob: introduce the SLOB allocator Matt Mackall
2005-11-01 20:51 ` Rob Landley [this message]
2005-11-01 21:06 ` Matt Mackall
2005-11-02 6:00 ` [PATCH 1/2] slob: move kstrdup to lib/string.c Andrew Morton
2005-11-02 7:03 ` Matt Mackall
2005-11-02 6:40 ` Andrew Morton
2005-11-02 9:17 ` Paul Mackerras
2005-11-02 13:04 ` Olaf Hering
2005-11-02 14:14 ` Tom Rini
2005-11-02 14:19 ` Olaf Hering
2005-11-02 14:31 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2005-11-03 23:00 [PATCH 1/2] slob: introduce mm/util.c for shared functions Matt Mackall
2005-11-03 23:00 ` [PATCH 2/2] slob: introduce the SLOB allocator Matt Mackall
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=200511011451.55362.rob@landley.net \
--to=rob@landley.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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