linux-kernel - SLUB vs SLAB allocator with respect to 3.x and 4.x kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAA=4087iJxxmZwJcsedMw_PRj-_iN3pSt63v5KgStX07L5He-w@mail.gmail.com>
Date:	Thu, 27 Aug 2015 19:56:43 +0530
From:	Navin Parakkal <navinp1912@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: SLUB vs SLAB allocator with respect to 3.x and 4.x kernels

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)



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