From: Glauber Costa <glommer@gmail.com>
To: linux-mm@kvack.org
Cc: akpm@linux-foundation.org, mhocko@suze.cz, hannes@cmpxchg.org,
kamezawa.hiroyu@jp.fujitsu.com,
Glauber Costa <glommer@openvz.org>
Subject: [PATCH v2 0/2] do not account memory used for cache creation
Date: Sun, 9 Jun 2013 16:45:52 +0400 [thread overview]
Message-ID: <1370781954-9972-1-git-send-email-glommer@openvz.org> (raw)
The memory we used to hold the memcg arrays is currently accounted to
the current memcg. But that creates a problem, because that memory can
only be freed after the last user is gone. Our only way to know which is
the last user, is to hook up to freeing time, but the fact that we still
have some in flight kmallocs will prevent freeing to happen. I believe
therefore to be just easier to account this memory as global overhead.
>From my last submission, Michal rightfully noted that this will break
when SLUB is used and allocations are big enough, since those will bypass
the cache mechanism and go directly to the page allocator. To fix this,
we need an extra patch that instructs the memcg kmem page charging to check
the bypass flag as well.
Glauber Costa (2):
memcg: also test for skip accounting at the page allocation level
memcg: do not account memory used for cache creation
mm/memcontrol.c | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
--
1.8.2.1
--
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>
next reply other threads:[~2013-06-09 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 12:45 Glauber Costa [this message]
2013-06-09 12:45 ` [PATCH v2 1/2] memcg: also test for skip accounting at the page allocation level Glauber Costa
2013-06-09 12:45 ` [PATCH v2 2/2] memcg: do not account memory used for cache creation Glauber Costa
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=1370781954-9972-1-git-send-email-glommer@openvz.org \
--to=glommer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=glommer@openvz.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suze.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;
as well as URLs for NNTP newsgroup(s).