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
| ||
|
Date: Thu, 27 Oct 2016 10:55:39 -0400 (EDT) From: David Miller <davem@...emloft.net> To: nitin.m.gupta@...cle.com Cc: sowmini.varadhan@...cle.com, aaron.young@...cle.com, bp@...e.de, sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] sparc64: Make SLUB the default allocator From: Nitin Gupta <nitin.m.gupta@...cle.com> Date: Wed, 26 Oct 2016 15:27:56 -0700 > SLUB has better debugging support. > > Signed-off-by: Nitin Gupta <nitin.m.gupta@...cle.com> ... > @@ -7,7 +7,9 @@ CONFIG_LOG_BUF_SHIFT=18 > CONFIG_BLK_DEV_INITRD=y > CONFIG_PERF_EVENTS=y > # CONFIG_COMPAT_BRK is not set > -CONFIG_SLAB=y > +CONFIG_SLUB_DEBUG=y > +CONFIG_SLUB=y > +CONFIG_SLUB_CPU_PARTIAL=y > CONFIG_PROFILING=y > CONFIG_OPROFILE=m > CONFIG_KPROBES=y This patch made me try to find guidance on other architectures as to what they put in their defconfig files. And it seems to me that they leave things like this to the user, and the defconfig only really contains things that really are required by the architecture or are architecture specific. So maybe instead of making arbitrary choices for these values which one set of users want and another set of users do not (I prefer SLAB, it is faster, and I know what the downsides wrt. NUMA balancing compared to SLAB are and am willing to accept that), we should do what other platforms do and not specify things like this at all.
Powered by blists - more mailing lists