All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov@parallels.com>
To: mhocko@suse.cz, akpm@linux-foundation.org
Cc: glommer@gmail.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, cgroups@vger.kernel.org, devel@openvz.org
Subject: [PATCH RESEND 00/11] kmemcg-fixes
Date: Mon, 6 Jan 2014 12:44:51 +0400	[thread overview]
Message-ID: <cover.1388996525.git.vdavydov@parallels.com> (raw)

Hi,

This patch-set fixes several bugs here and there in the implementation
of kmem accounting for memory cgroups and hopefully makes the code look
a bit clearer.

Links to discussion threads that led to this patch-set:
http://www.spinics.net/lists/cgroups/msg09512.html
http://www.spinics.net/lists/cgroups/msg09695.html
http://www.spinics.net/lists/cgroups/msg09796.html

Any comments are highly appreciated.

Thanks.

Vladimir Davydov (11):
  slab: cleanup kmem_cache_create_memcg() error handling
  memcg, slab: kmem_cache_create_memcg(): fix memleak on fail path
  memcg, slab: cleanup memcg cache initialization/destruction
  memcg, slab: fix barrier usage when accessing memcg_caches
  memcg: fix possible NULL deref while traversing memcg_slab_caches
    list
  memcg, slab: fix races in per-memcg cache creation/destruction
  memcg: get rid of kmem_cache_dup
  slab: do not panic if we fail to create memcg cache
  memcg, slab: RCU protect memcg_params for root caches
  memcg: remove KMEM_ACCOUNTED_ACTIVATED flag
  memcg: rework memcg_update_kmem_limit synchronization

 include/linux/memcontrol.h |   23 +--
 include/linux/slab.h       |    9 +-
 mm/memcontrol.c            |  405 +++++++++++++++++++++-----------------------
 mm/slab.h                  |   26 ++-
 mm/slab_common.c           |   90 ++++++----
 5 files changed, 292 insertions(+), 261 deletions(-)

-- 
1.7.10.4

--
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>, <akpm@linux-foundation.org>
Cc: <glommer@gmail.com>, <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>, <cgroups@vger.kernel.org>,
	<devel@openvz.org>
Subject: [PATCH RESEND 00/11] kmemcg-fixes
Date: Mon, 6 Jan 2014 12:44:51 +0400	[thread overview]
Message-ID: <cover.1388996525.git.vdavydov@parallels.com> (raw)

Hi,

This patch-set fixes several bugs here and there in the implementation
of kmem accounting for memory cgroups and hopefully makes the code look
a bit clearer.

Links to discussion threads that led to this patch-set:
http://www.spinics.net/lists/cgroups/msg09512.html
http://www.spinics.net/lists/cgroups/msg09695.html
http://www.spinics.net/lists/cgroups/msg09796.html

Any comments are highly appreciated.

Thanks.

Vladimir Davydov (11):
  slab: cleanup kmem_cache_create_memcg() error handling
  memcg, slab: kmem_cache_create_memcg(): fix memleak on fail path
  memcg, slab: cleanup memcg cache initialization/destruction
  memcg, slab: fix barrier usage when accessing memcg_caches
  memcg: fix possible NULL deref while traversing memcg_slab_caches
    list
  memcg, slab: fix races in per-memcg cache creation/destruction
  memcg: get rid of kmem_cache_dup
  slab: do not panic if we fail to create memcg cache
  memcg, slab: RCU protect memcg_params for root caches
  memcg: remove KMEM_ACCOUNTED_ACTIVATED flag
  memcg: rework memcg_update_kmem_limit synchronization

 include/linux/memcontrol.h |   23 +--
 include/linux/slab.h       |    9 +-
 mm/memcontrol.c            |  405 +++++++++++++++++++++-----------------------
 mm/slab.h                  |   26 ++-
 mm/slab_common.c           |   90 ++++++----
 5 files changed, 292 insertions(+), 261 deletions(-)

-- 
1.7.10.4


             reply	other threads:[~2014-01-06  8:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06  8:44 Vladimir Davydov [this message]
2014-01-06  8:44 ` [PATCH RESEND 00/11] kmemcg-fixes Vladimir Davydov
2014-01-06  8:44 ` [PATCH RESEND 01/11] slab: cleanup kmem_cache_create_memcg() error handling Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
2014-01-06  8:44 ` [PATCH RESEND 02/11] memcg, slab: kmem_cache_create_memcg(): fix memleak on fail path Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
2014-01-06  8:44 ` [PATCH RESEND 03/11] memcg, slab: cleanup memcg cache initialization/destruction Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
2014-01-06  8:44 ` [PATCH RESEND 04/11] memcg, slab: fix barrier usage when accessing memcg_caches Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
2014-01-06  8:44 ` [PATCH RESEND 05/11] memcg: fix possible NULL deref while traversing memcg_slab_caches list Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
2014-01-06  8:44 ` [PATCH RESEND 06/11] memcg, slab: fix races in per-memcg cache creation/destruction Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
2014-01-06  8:44 ` [PATCH RESEND 07/11] memcg: get rid of kmem_cache_dup Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
2014-01-06  8:44 ` [PATCH RESEND 08/11] slab: do not panic if we fail to create memcg cache Vladimir Davydov
2014-01-06  8:44   ` Vladimir Davydov
     [not found] ` <cover.1388996525.git.vdavydov-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2014-01-06  8:45   ` [PATCH RESEND 09/11] memcg, slab: RCU protect memcg_params for root caches Vladimir Davydov
2014-01-06  8:45     ` Vladimir Davydov
2014-01-06  8:45     ` Vladimir Davydov
2014-01-06  8:45 ` [PATCH RESEND 10/11] memcg: remove KMEM_ACCOUNTED_ACTIVATED flag Vladimir Davydov
2014-01-06  8:45   ` Vladimir Davydov
2014-01-06  8:45 ` [PATCH RESEND 11/11] memcg: rework memcg_update_kmem_limit synchronization Vladimir Davydov
2014-01-06  8:45   ` 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=cover.1388996525.git.vdavydov@parallels.com \
    --to=vdavydov@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=devel@openvz.org \
    --cc=glommer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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.