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  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:   Sun, 29 Jan 2017 19:04:17 +0300
From:   Vladimir Davydov <>
To:     Tejun Heo <>
Subject: Re: [PATCH 10/10] slab: use memcg_kmem_cache_wq for slab destruction

On Tue, Jan 17, 2017 at 03:54:11PM -0800, Tejun Heo wrote:
> If there's contention on slab_mutex, queueing the per-cache
> destruction work item on the system_wq can unnecessarily create and
> tie up a lot of kworkers.
> Rename memcg_kmem_cache_create_wq to memcg_kmem_cache_wq and make it
> global and use that workqueue for the destruction work items too.
> While at it, convert the workqueue from an unbound workqueue to a
> per-cpu one with concurrency limited to 1.  It's generally preferable
> to use per-cpu workqueues and concurrency limit of 1 is safe enough.
> This is suggested by Joonsoo Kim.
> Signed-off-by: Tejun Heo <>
> Reported-by: Jay Vana <>
> Cc: Vladimir Davydov <>
> Cc: Christoph Lameter <>
> Cc: Pekka Enberg <>
> Cc: David Rientjes <>
> Cc: Joonsoo Kim <>
> Cc: Andrew Morton <>

Acked-by: Vladimir Davydov <>

Powered by blists - more mailing lists