From: Ezequiel Garcia <elezegarcia@gmail.com>
To: linux-mm@kvack.org
Subject: sl[aou]b allocator comparison
Date: Tue, 2 Oct 2012 08:22:41 -0300 [thread overview]
Message-ID: <CALF0-+UvHP2RTGwPuHM1HE0VTBWUm_pDATap7C5V7+MMqwbdsA@mail.gmail.com> (raw)
Hello,
I'd like to know what's the current status of each allocator regarding
its targeted scenario.
According to my numbers:
* slob
very small static footprint, low internal fragmentation, doesn't scale well.
targeted at really small embedded.
* slub
default allocator, low internal fragmentation, suites well most scenarios.
* slab
high internal fragmentation, we still have it because slub showed some unfixed
(performance?) regression in some scenario.
Anyone can add anything useful to this quick comparison?
Thanks,
Ezequiel.
--
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:[~2012-10-02 11:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CALF0-+UvHP2RTGwPuHM1HE0VTBWUm_pDATap7C5V7+MMqwbdsA@mail.gmail.com \
--to=elezegarcia@gmail.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).