[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALvZod44+GuDxXSqWOZB3uhvdxJeH+vnXevx+=iy-azv74ueqA@mail.gmail.com>
Date: Tue, 25 Jun 2019 11:17:41 -0700
From: Shakeel Butt <shakeelb@...gle.com>
To: Roman Gushchin <guro@...com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Vladimir Davydov <vdavydov.dev@...il.com>,
Linux MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Kernel Team <kernel-team@...com>,
Johannes Weiner <hannes@...xchg.org>,
Waiman Long <longman@...hat.com>
Subject: Re: [PATCH v7 03/10] mm: generalize postponed non-root kmem_cache deactivation
On Tue, Jun 11, 2019 at 4:18 PM Roman Gushchin <guro@...com> wrote:
>
> Currently SLUB uses a work scheduled after an RCU grace period
> to deactivate a non-root kmem_cache. This mechanism can be reused
> for kmem_caches release, but requires generalization for SLAB
> case.
>
> Introduce kmemcg_cache_deactivate() function, which calls
> allocator-specific __kmem_cache_deactivate() and schedules
> execution of __kmem_cache_deactivate_after_rcu() with all
> necessary locks in a worker context after an rcu grace period.
>
> Here is the new calling scheme:
> kmemcg_cache_deactivate()
> __kmemcg_cache_deactivate() SLAB/SLUB-specific
> kmemcg_rcufn() rcu
> kmemcg_workfn() work
> __kmemcg_cache_deactivate_after_rcu() SLAB/SLUB-specific
>
> instead of:
> __kmemcg_cache_deactivate() SLAB/SLUB-specific
> slab_deactivate_memcg_cache_rcu_sched() SLUB-only
> kmemcg_rcufn() rcu
> kmemcg_workfn() work
> kmemcg_cache_deact_after_rcu() SLUB-only
>
> For consistency, all allocator-specific functions start with "__".
>
> Signed-off-by: Roman Gushchin <guro@...com>
> Acked-by: Vladimir Davydov <vdavydov.dev@...il.com>
Reviewed-by: Shakeel Butt <shakeelb@...gle.com>
Powered by blists - more mailing lists