linux-kernel - Re: [patch] slub: default min_partial to at least highest cpus per node

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 7 Apr 2009 15:03:48 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Christoph Lameter <cl@...ux.com>
cc:	Pekka Enberg <penberg@...helsinki.fi>, linux-kernel@...r.kernel.org
Subject: Re: [patch] slub: default min_partial to at least highest cpus per
  node

On Tue, 7 Apr 2009, Christoph Lameter wrote:

> > Right, but right now allocating new slabs is extremely slow compared to
> > using a partial slab.
> 
> Work on the page allocator is in progress. So this is band aid until the
> work on the page allocator is complete. Maybe better focus on helping Mel?
> 

The page allocator may be getting significantly faster, but that is _not_ 
the only reason why we use partial slabs.  Higher order slabs, such as the 
default for kmalloc-2048, kmalloc-4096, etc., increase the liklihood of 
having cpu slabs at that order as opposed to order fallback with a 
sufficiently long uptime.
--
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/