From: Vladimir Davydov <vdavydov@parallels.com>
To: mhocko@suse.cz, hannes@cmpxchg.org
Cc: akpm@linux-foundation.org, glommer@gmail.com,
cl@linux-foundation.org, penberg@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
devel@openvz.org
Subject: Re: [PATCH RFC -mm v2 0/3] kmemcg: simplify work-flow (was "memcg-vs-slab cleanup")
Date: Fri, 18 Apr 2014 12:08:10 +0400 [thread overview]
Message-ID: <5350DD6A.1020804@parallels.com> (raw)
In-Reply-To: <cover.1397804745.git.vdavydov@parallels.com>
On 04/18/2014 12:04 PM, Vladimir Davydov wrote:
> Hi Michal, Johannes,
>
> This patch-set is a part of preparations for kmemcg re-parenting. It
> targets at simplifying kmemcg work-flows and synchronization.
>
> First, it removes async per memcg cache destruction (see patches 1, 2).
> Now caches are only destroyed on memcg offline. That means the caches
> that are not empty on memcg offline will be leaked. However, they are
> already leaked, because memcg_cache_params::nr_pages normally never
> drops to 0 so the destruction work is never scheduled except
> kmem_cache_shrink is called explicitly. In the future I'm planning
> reaping such dead caches on vmpressure or periodically.
>
> Second, it substitutes per memcg slab_caches_mutex's with the global
> memcg_slab_mutex, which should be taken during the whole per memcg cache
> creation/destruction path before the slab_mutex (see patch 3). This
> greatly simplifies synchronization among various per memcg cache
> creation/destruction paths.
v1 can be found here: https://lkml.org/lkml/2014/4/9/298
Changes in v2:
- substitute per memcg slab_caches_mutex's with the global
memcg_slab_mutex and re-split the set.
>
> I really need your help, because I'm far not sure if what I'm doing here
> is right. So I would appreciate if you could look through the patches
> and share your thoughts about the design changes they introduce.
>
> Thanks,
>
> Vladimir Davydov (3):
> memcg, slab: do not schedule cache destruction when last page goes
> away
> memcg, slab: merge memcg_{bind,release}_pages to
> memcg_{un}charge_slab
> memcg, slab: simplify synchronization scheme
>
> include/linux/memcontrol.h | 15 +--
> include/linux/slab.h | 8 +-
> mm/memcontrol.c | 231 +++++++++++++++-----------------------------
> mm/slab.c | 2 -
> mm/slab.h | 28 +-----
> mm/slab_common.c | 22 ++---
> mm/slub.c | 2 -
> 7 files changed, 92 insertions(+), 216 deletions(-)
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Davydov <vdavydov@parallels.com>
To: <mhocko@suse.cz>, <hannes@cmpxchg.org>
Cc: <akpm@linux-foundation.org>, <glommer@gmail.com>,
<cl@linux-foundation.org>, <penberg@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<devel@openvz.org>
Subject: Re: [PATCH RFC -mm v2 0/3] kmemcg: simplify work-flow (was "memcg-vs-slab cleanup")
Date: Fri, 18 Apr 2014 12:08:10 +0400 [thread overview]
Message-ID: <5350DD6A.1020804@parallels.com> (raw)
In-Reply-To: <cover.1397804745.git.vdavydov@parallels.com>
On 04/18/2014 12:04 PM, Vladimir Davydov wrote:
> Hi Michal, Johannes,
>
> This patch-set is a part of preparations for kmemcg re-parenting. It
> targets at simplifying kmemcg work-flows and synchronization.
>
> First, it removes async per memcg cache destruction (see patches 1, 2).
> Now caches are only destroyed on memcg offline. That means the caches
> that are not empty on memcg offline will be leaked. However, they are
> already leaked, because memcg_cache_params::nr_pages normally never
> drops to 0 so the destruction work is never scheduled except
> kmem_cache_shrink is called explicitly. In the future I'm planning
> reaping such dead caches on vmpressure or periodically.
>
> Second, it substitutes per memcg slab_caches_mutex's with the global
> memcg_slab_mutex, which should be taken during the whole per memcg cache
> creation/destruction path before the slab_mutex (see patch 3). This
> greatly simplifies synchronization among various per memcg cache
> creation/destruction paths.
v1 can be found here: https://lkml.org/lkml/2014/4/9/298
Changes in v2:
- substitute per memcg slab_caches_mutex's with the global
memcg_slab_mutex and re-split the set.
>
> I really need your help, because I'm far not sure if what I'm doing here
> is right. So I would appreciate if you could look through the patches
> and share your thoughts about the design changes they introduce.
>
> Thanks,
>
> Vladimir Davydov (3):
> memcg, slab: do not schedule cache destruction when last page goes
> away
> memcg, slab: merge memcg_{bind,release}_pages to
> memcg_{un}charge_slab
> memcg, slab: simplify synchronization scheme
>
> include/linux/memcontrol.h | 15 +--
> include/linux/slab.h | 8 +-
> mm/memcontrol.c | 231 +++++++++++++++-----------------------------
> mm/slab.c | 2 -
> mm/slab.h | 28 +-----
> mm/slab_common.c | 22 ++---
> mm/slub.c | 2 -
> 7 files changed, 92 insertions(+), 216 deletions(-)
>
next prev parent reply other threads:[~2014-04-18 8:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 8:04 [PATCH RFC -mm v2 0/3] kmemcg: simplify work-flow (was "memcg-vs-slab cleanup") Vladimir Davydov
2014-04-18 8:04 ` Vladimir Davydov
2014-04-18 8:04 ` [PATCH RFC -mm v2 1/3] memcg, slab: do not schedule cache destruction when last page goes away Vladimir Davydov
2014-04-18 8:04 ` Vladimir Davydov
2014-04-18 13:41 ` Johannes Weiner
2014-04-18 13:41 ` Johannes Weiner
2014-04-18 16:05 ` Vladimir Davydov
2014-04-18 16:05 ` Vladimir Davydov
2014-04-18 8:04 ` [PATCH RFC -mm v2 2/3] memcg, slab: merge memcg_{bind,release}_pages to memcg_{un}charge_slab Vladimir Davydov
2014-04-18 8:04 ` Vladimir Davydov
2014-04-18 13:44 ` Johannes Weiner
2014-04-18 13:44 ` Johannes Weiner
2014-04-18 16:07 ` Vladimir Davydov
2014-04-18 16:07 ` Vladimir Davydov
2014-04-18 8:04 ` [PATCH RFC -mm v2 3/3] memcg, slab: simplify synchronization scheme Vladimir Davydov
2014-04-18 8:04 ` Vladimir Davydov
2014-04-18 14:17 ` Johannes Weiner
2014-04-18 14:17 ` Johannes Weiner
2014-04-18 16:08 ` Vladimir Davydov
2014-04-18 16:08 ` Vladimir Davydov
2014-04-18 18:26 ` Johannes Weiner
2014-04-18 18:26 ` Johannes Weiner
2014-04-18 8:08 ` Vladimir Davydov [this message]
2014-04-18 8:08 ` [PATCH RFC -mm v2 0/3] kmemcg: simplify work-flow (was "memcg-vs-slab cleanup") Vladimir Davydov
2014-04-18 13:23 ` Johannes Weiner
2014-04-18 13:23 ` Johannes Weiner
2014-04-18 16:04 ` Vladimir Davydov
2014-04-18 16:04 ` Vladimir Davydov
2014-04-20 10:32 ` Vladimir Davydov
2014-04-20 10:32 ` Vladimir Davydov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5350DD6A.1020804@parallels.com \
--to=vdavydov@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=devel@openvz.org \
--cc=glommer@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=penberg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.