From: Vladimir Davydov <vdavydov@parallels.com>
To: akpm@linux-foundation.org
Cc: mhocko@suse.cz, hannes@cmpxchg.org, cl@linux.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 0/6] memcg: release memcg_cache_id on css offline
Date: Wed, 23 Jul 2014 14:53:12 +0400 [thread overview]
Message-ID: <20140723105312.GC30850@esperanza> (raw)
In-Reply-To: <cover.1405941342.git.vdavydov@parallels.com>
On Mon, Jul 21, 2014 at 03:47:10PM +0400, Vladimir Davydov wrote:
> This patch set makes memcg release memcg_cache_id on css offline. This
> way the memcg_caches arrays size will be limited by the number of alive
> kmem-active memory cgroups, which is much better.
Hi Andrew,
While preparing the per-memcg slab shrinkers patch set, I realized that
releasing memcg_cache_id on css offline is incorrect, because after css
offline there still can be elements on per-memcg list_lrus, which are
indexed by memcg_cache_id. We could re-parent them, but this is what we
decided to avoid in order to keep things clean and simple. So it seems
there's nothing we can do except keeping memcg_cache_ids till css free.
I wonder if we could reclaim memory from per memcg arrays (per memcg
list_lrus, kmem_caches) on memory pressure. May be, we could use
flex_array to achieve that.
Anyway, could you please drop the following patches from the mmotm tree
(all this set except patch 1, which is a mere cleanup)?
memcg-release-memcg_cache_id-on-css-offline
memcg-keep-all-children-of-each-root-cache-on-a-list
memcg-add-pointer-to-owner-cache-to-memcg_cache_params
memcg-make-memcg_cache_id-static
slab-use-mem_cgroup_id-for-per-memcg-cache-naming
Sorry about the noise.
Thank you.
--
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>
prev parent reply other threads:[~2014-07-23 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 11:47 Vladimir Davydov
2014-07-21 11:47 ` [PATCH -mm 1/6] slub: remove kmemcg id from create_unique_id Vladimir Davydov
2014-07-21 11:47 ` [PATCH -mm 2/6] slab: use mem_cgroup_id for per memcg cache naming Vladimir Davydov
2014-07-21 11:47 ` [PATCH -mm 3/6] memcg: make memcg_cache_id static Vladimir Davydov
2014-07-21 11:47 ` [PATCH -mm 4/6] memcg: add pointer to owner cache to memcg_cache_params Vladimir Davydov
2014-07-21 11:47 ` [PATCH -mm 5/6] memcg: keep all children of each root cache on a list Vladimir Davydov
2014-07-21 11:47 ` [PATCH -mm 6/6] memcg: release memcg_cache_id on css offline Vladimir Davydov
2014-07-23 10:53 ` Vladimir Davydov [this message]
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=20140723105312.GC30850@esperanza \
--to=vdavydov@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox