From: Vladimir Davydov <vdavydov@virtuozzo.com>
To: Tejun Heo <tj@kernel.org>
Cc: Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Greg Thelen <gthelen@google.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] memcg/kmem: switch to white list policy
Date: Tue, 10 Nov 2015 10:49:14 +0300 [thread overview]
Message-ID: <20151110074914.GQ31308@esperanza> (raw)
In-Reply-To: <20151109203053.GD28507@mtj.duckdns.org>
On Mon, Nov 09, 2015 at 03:30:53PM -0500, Tejun Heo wrote:
...
> Hmm.... can't we simply merge among !SLAB_ACCOUNT and SLAB_ACCOUNT
> kmem_caches within themselves? I don't think we'd be losing anything
> by restricting merge at that level. For anything to be tagged
> SLAB_ACCOUNT, it has to have a potential to grow enormous after all.
OK, I'll prepare v2 which will introduce SLAB_ACCOUNT and add it to
SLAB_MERGE_SAME. Let's see what slab maintainers think of it.
Thanks,
Vladimir
--
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@virtuozzo.com>
To: Tejun Heo <tj@kernel.org>
Cc: Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Greg Thelen <gthelen@google.com>, <linux-mm@kvack.org>,
<cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] memcg/kmem: switch to white list policy
Date: Tue, 10 Nov 2015 10:49:14 +0300 [thread overview]
Message-ID: <20151110074914.GQ31308@esperanza> (raw)
In-Reply-To: <20151109203053.GD28507@mtj.duckdns.org>
On Mon, Nov 09, 2015 at 03:30:53PM -0500, Tejun Heo wrote:
...
> Hmm.... can't we simply merge among !SLAB_ACCOUNT and SLAB_ACCOUNT
> kmem_caches within themselves? I don't think we'd be losing anything
> by restricting merge at that level. For anything to be tagged
> SLAB_ACCOUNT, it has to have a potential to grow enormous after all.
OK, I'll prepare v2 which will introduce SLAB_ACCOUNT and add it to
SLAB_MERGE_SAME. Let's see what slab maintainers think of it.
Thanks,
Vladimir
next prev parent reply other threads:[~2015-11-10 7:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 20:07 [PATCH 0/5] memcg/kmem: switch to white list policy Vladimir Davydov
2015-11-07 20:07 ` Vladimir Davydov
2015-11-07 20:07 ` Vladimir Davydov
[not found] ` <cover.1446924358.git.vdavydov-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2015-11-07 20:07 ` [PATCH 1/5] Revert "kernfs: do not account ino_ida allocations to memcg" Vladimir Davydov
2015-11-07 20:07 ` Vladimir Davydov
2015-11-07 20:07 ` Vladimir Davydov
2015-11-07 20:07 ` [PATCH 2/5] Revert "gfp: add __GFP_NOACCOUNT" Vladimir Davydov
2015-11-07 20:07 ` Vladimir Davydov
2015-11-07 20:07 ` [PATCH 3/5] memcg: only account kmem allocations marked as __GFP_ACCOUNT Vladimir Davydov
2015-11-07 20:07 ` Vladimir Davydov
2015-11-07 20:07 ` [PATCH 4/5] vmalloc: allow to account vmalloc to memcg Vladimir Davydov
2015-11-07 20:07 ` Vladimir Davydov
2015-11-07 20:07 ` [PATCH 5/5] Account certain kmem allocations " Vladimir Davydov
2015-11-07 20:07 ` Vladimir Davydov
2015-11-09 14:39 ` Michal Hocko
2015-11-09 14:39 ` Michal Hocko
[not found] ` <20151109143955.GF8916-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-11-10 8:07 ` Vladimir Davydov
2015-11-10 8:07 ` Vladimir Davydov
2015-11-10 8:07 ` Vladimir Davydov
2015-11-10 13:23 ` Michal Hocko
2015-11-10 13:23 ` Michal Hocko
2015-11-10 13:23 ` Michal Hocko
2015-11-09 14:08 ` [PATCH 0/5] memcg/kmem: switch to white list policy Michal Hocko
2015-11-09 14:08 ` Michal Hocko
2015-11-09 16:45 ` Johannes Weiner
2015-11-09 16:45 ` Johannes Weiner
[not found] ` <20151109140832.GE8916-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-11-09 18:28 ` Vladimir Davydov
2015-11-09 18:28 ` Vladimir Davydov
2015-11-09 18:28 ` Vladimir Davydov
2015-11-09 18:54 ` Tejun Heo
2015-11-09 18:54 ` Tejun Heo
[not found] ` <20151109185401.GB28507-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2015-11-09 19:27 ` Vladimir Davydov
2015-11-09 19:27 ` Vladimir Davydov
2015-11-09 19:27 ` Vladimir Davydov
2015-11-09 19:32 ` Tejun Heo
2015-11-09 19:32 ` Tejun Heo
[not found] ` <20151109193253.GC28507-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2015-11-09 20:12 ` Vladimir Davydov
2015-11-09 20:12 ` Vladimir Davydov
2015-11-09 20:12 ` Vladimir Davydov
2015-11-09 20:30 ` Tejun Heo
2015-11-09 20:30 ` Tejun Heo
2015-11-09 20:30 ` Tejun Heo
2015-11-10 7:49 ` Vladimir Davydov [this message]
2015-11-10 7:49 ` Vladimir Davydov
2015-11-11 8:12 ` Michal Hocko
2015-11-11 8:12 ` Michal Hocko
2015-11-11 8:12 ` Michal Hocko
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=20151110074914.GQ31308@esperanza \
--to=vdavydov@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=tj@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.