[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170203174346.GA26336@mtj.duckdns.org>
Date: Fri, 3 Feb 2017 12:43:46 -0500
From: Tejun Heo <tj@...nel.org>
To: vdavydov.dev@...il.com, cl@...ux.com, penberg@...nel.org,
rientjes@...gle.com, iamjoonsoo.kim@....com,
akpm@...ux-foundation.org
Cc: jsvana@...com, hannes@...xchg.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, cgroups@...r.kernel.org, kernel-team@...com
Subject: Re: [PATCHSET v3] slab: make memcg slab destruction scalable
Hello,
On Tue, Jan 17, 2017 at 03:54:01PM -0800, Tejun Heo wrote:
> Changes from [V2] to V3.
>
> * 0002-slub-separate-out-sysfs_slab_release-from-sysfs_slab.patch
> separated out from
> 0002-slab-remove-synchronous-rcu_barrier-call-in-memcg-ca.patch.
>
> * 0002-slab-remove-synchronous-rcu_barrier-call-in-memcg-ca.patch
> replaced with
> 0003-slab-remove-synchronous-rcu_barrier-call-in-memcg-ca.patch.
> It now keeps rcu_barrier() in the kmem_cache destruction path.
>
> * 0010-slab-memcg-wq.patch added to limit concurrency on destruction
> work items.
Are there more concerns on this patchset? If not, Andrew, can you
please route these patches? On certain setups, this can cause serious
performance and scalability issues.
Thanks.
--
tejun
Powered by blists - more mailing lists