From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Navin Parakkal <navinp1912@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: SLUB vs SLAB allocator with respect to 3.x and 4.x kernels
Date: Thu, 27 Aug 2015 15:43:42 -0400 [thread overview]
Message-ID: <55DF686E.50309@gmail.com> (raw)
In-Reply-To: <CAA=4087iJxxmZwJcsedMw_PRj-_iN3pSt63v5KgStX07L5He-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On 2015-08-27 10:26, Navin Parakkal wrote:
> Hi,
>
> I found that in many worst case scenarios like fragmention of
> allocator , slub performs well than slab.
> I also noticed that Centos /Ubuntu etc switched to SLUB but SLES
> still uses SLAB in the default image.
>
> Any particular reason where SLAB is the choice ?
>
>
> I ask this since i find SLUB to be the default choice since 2.6.23 as
> per https://en.wikipedia.org/wiki/SLUB_(software)
>
IIRC, SLUB isn't available/reliable on some arches (that and in some
setups, the worst case scenarios are likely to never happen (for
example, a machine with 1T of RAM that get's rebooted daily isn't likely
to have significant issues with memory fragmentation)).
SLES probably hasn't switched because they're an enterprise distro,
which in turn means changing as little as possible when updating.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-08-27 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 14:26 SLUB vs SLAB allocator with respect to 3.x and 4.x kernels Navin Parakkal
2015-08-27 19:43 ` Austin S Hemmelgarn [this message]
2015-08-27 21:06 ` David Rientjes
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=55DF686E.50309@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=navinp1912@gmail.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 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.