From: Vladimir Davydov <vdavydov@parallels.com>
To: Michal Hocko <mhocko@suse.cz>, glommer@gmail.com
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
devel@openvz.org, Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH -mm 1/4] sl[au]b: do not charge large allocations to memcg
Date: Thu, 27 Mar 2014 11:34:10 +0400 [thread overview]
Message-ID: <5333D472.2000606@parallels.com> (raw)
In-Reply-To: <20140326215320.GA22656@dhcp22.suse.cz>
Hi Michal,
On 03/27/2014 01:53 AM, Michal Hocko wrote:
> On Wed 26-03-14 19:28:04, Vladimir Davydov wrote:
>> We don't track any random page allocation, so we shouldn't track kmalloc
>> that falls back to the page allocator.
> Why did we do that in the first place? d79923fad95b (sl[au]b: allocate
> objects from memcg cache) didn't tell me much.
I don't know, we'd better ask Glauber about that.
> How is memcg_kmem_skip_account removal related?
The comment this patch removes along with the memcg_kmem_skip_account
check explains that pretty well IMO. In short, we only use
memcg_kmem_skip_account to prevent kmalloc's from charging, which is
crucial for recursion-avoidance in memcg_kmem_get_cache. Since we don't
charge pages allocated from a root (not per-memcg) cache, from the first
glance it would be enough to check for memcg_kmem_skip_account only in
memcg_kmem_get_cache and return the root cache if it's set. However, for
we can also kmalloc w/o issuing memcg_kmem_get_cache (kmalloc_large), we
also need this check in memcg_kmem_newpage_charge. This patch removes
kmalloc_large accounting, so we don't need this check anymore.
Thanks.
--
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: Michal Hocko <mhocko@suse.cz>, <glommer@gmail.com>
Cc: <akpm@linux-foundation.org>, <hannes@cmpxchg.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<devel@openvz.org>, Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH -mm 1/4] sl[au]b: do not charge large allocations to memcg
Date: Thu, 27 Mar 2014 11:34:10 +0400 [thread overview]
Message-ID: <5333D472.2000606@parallels.com> (raw)
In-Reply-To: <20140326215320.GA22656@dhcp22.suse.cz>
Hi Michal,
On 03/27/2014 01:53 AM, Michal Hocko wrote:
> On Wed 26-03-14 19:28:04, Vladimir Davydov wrote:
>> We don't track any random page allocation, so we shouldn't track kmalloc
>> that falls back to the page allocator.
> Why did we do that in the first place? d79923fad95b (sl[au]b: allocate
> objects from memcg cache) didn't tell me much.
I don't know, we'd better ask Glauber about that.
> How is memcg_kmem_skip_account removal related?
The comment this patch removes along with the memcg_kmem_skip_account
check explains that pretty well IMO. In short, we only use
memcg_kmem_skip_account to prevent kmalloc's from charging, which is
crucial for recursion-avoidance in memcg_kmem_get_cache. Since we don't
charge pages allocated from a root (not per-memcg) cache, from the first
glance it would be enough to check for memcg_kmem_skip_account only in
memcg_kmem_get_cache and return the root cache if it's set. However, for
we can also kmalloc w/o issuing memcg_kmem_get_cache (kmalloc_large), we
also need this check in memcg_kmem_newpage_charge. This patch removes
kmalloc_large accounting, so we don't need this check anymore.
Thanks.
next prev parent reply other threads:[~2014-03-27 7:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 15:28 [PATCH -mm 0/4] kmemcg: get rid of __GFP_KMEMCG Vladimir Davydov
2014-03-26 15:28 ` Vladimir Davydov
2014-03-26 15:28 ` [PATCH -mm 1/4] sl[au]b: do not charge large allocations to memcg Vladimir Davydov
2014-03-26 15:28 ` Vladimir Davydov
2014-03-26 21:53 ` Michal Hocko
2014-03-26 21:53 ` Michal Hocko
2014-03-27 7:34 ` Vladimir Davydov [this message]
2014-03-27 7:34 ` Vladimir Davydov
2014-03-27 20:40 ` Michal Hocko
2014-03-27 20:40 ` Michal Hocko
2014-03-27 4:31 ` Greg Thelen
2014-03-27 4:31 ` Greg Thelen
2014-03-27 7:37 ` Vladimir Davydov
2014-03-27 7:37 ` Vladimir Davydov
2014-03-27 20:42 ` Greg Thelen
2014-03-27 20:42 ` Greg Thelen
2014-03-28 7:56 ` Vladimir Davydov
2014-03-28 7:56 ` Vladimir Davydov
2014-03-27 20:43 ` Michal Hocko
2014-03-27 20:43 ` Michal Hocko
2014-03-28 7:58 ` Vladimir Davydov
2014-03-28 7:58 ` Vladimir Davydov
2014-03-26 15:28 ` [PATCH -mm 2/4] sl[au]b: charge slabs to memcg explicitly Vladimir Davydov
2014-03-26 15:28 ` Vladimir Davydov
2014-03-26 21:58 ` Michal Hocko
2014-03-26 21:58 ` Michal Hocko
2014-03-27 7:38 ` Vladimir Davydov
2014-03-27 7:38 ` Vladimir Davydov
2014-03-27 20:38 ` Michal Hocko
2014-03-27 20:38 ` Michal Hocko
2014-03-26 15:28 ` [PATCH -mm 3/4] fork: charge threadinfo " Vladimir Davydov
2014-03-26 15:28 ` Vladimir Davydov
2014-03-26 22:00 ` Michal Hocko
2014-03-26 22:00 ` Michal Hocko
2014-03-27 7:39 ` Vladimir Davydov
2014-03-27 7:39 ` Vladimir Davydov
2014-03-26 15:28 ` [PATCH -mm 4/4] mm: kill __GFP_KMEMCG Vladimir Davydov
2014-03-26 15:28 ` 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=5333D472.2000606@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.