From: Pavel Emelyanov <xemul@parallels.com>
To: balbir@linux.vnet.ibm.com
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
David Rientjes <rientjes@google.com>,
Suleiman Souhlal <suleiman@google.com>,
Ying Han <yinghan@google.com>,
linux-mm@kvack.org
Subject: Re: memcg: slab control
Date: Wed, 02 Dec 2009 13:14:15 +0300 [thread overview]
Message-ID: <4B163DF7.60305@parallels.com> (raw)
In-Reply-To: <20091201151431.GV2970@balbir.in.ibm.com>
Balbir Singh wrote:
> * Pavel Emelyanov <xemul@parallels.com> [2009-12-01 13:40:30]:
>
>>> Just to understand the context better, is this really a problem. This
>>> can occur when we do really run out of memory. The idea of using
>>> slabcg + memcg together is good, except for our accounting process. I
>>> can repost percpu counter patches that adds fuzziness along with other
>>> tricks that Kame has to do batch accounting, that we will need to
>>> make sure we are able to do with slab allocations as well.
>>>
>> I'm not sure I understand you concern. Can you elaborate, please?
>>
>
> The concern was mostly accounting when memcg + slabcg are integrated
> into the same framework. res_counters will need new scalability
> primitives.
>
I see. I think the best we can do here is start with a separate controller.
--
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 prev parent reply other threads:[~2009-12-02 10:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 23:08 memcg: slab control David Rientjes
2009-11-26 1:14 ` KAMEZAWA Hiroyuki
2009-11-26 8:50 ` Balbir Singh
2009-11-26 8:56 ` KAMEZAWA Hiroyuki
2009-11-26 9:10 ` Pavel Emelyanov
2009-11-26 9:33 ` KAMEZAWA Hiroyuki
2009-11-26 9:56 ` Pavel Emelyanov
2009-11-26 10:24 ` Suleiman Souhlal
2009-11-26 12:31 ` Pavel Emelyanov
2009-11-26 12:52 ` Suleiman Souhlal
2009-12-01 7:40 ` Balbir Singh
2009-11-27 7:15 ` Ying Han
2009-11-27 9:45 ` Pavel Emelyanov
2009-12-01 5:14 ` KOSAKI Motohiro
2009-11-30 22:57 ` David Rientjes
2009-12-01 10:31 ` Pavel Emelyanov
2009-12-01 22:29 ` David Rientjes
2009-12-01 7:36 ` Balbir Singh
2009-12-01 10:40 ` Pavel Emelyanov
2009-12-01 15:14 ` Balbir Singh
2009-12-02 10:14 ` Pavel Emelyanov [this message]
2009-12-02 10:19 ` Balbir Singh
2009-12-02 10:51 ` Pavel Emelyanov
2009-11-30 22:55 ` David Rientjes
2009-12-01 10:39 ` Pavel Emelyanov
2009-11-26 10:13 ` Suleiman Souhlal
2009-11-30 9:17 ` Balbir Singh
2009-11-30 22:45 ` David Rientjes
2009-11-26 1:17 ` KAMEZAWA Hiroyuki
2009-11-26 10:01 ` Suleiman Souhlal
2009-11-26 2:35 ` KOSAKI Motohiro
2009-11-27 7:01 ` Ying Han
2009-11-27 9:48 ` Pavel Emelyanov
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=4B163DF7.60305@parallels.com \
--to=xemul@parallels.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=suleiman@google.com \
--cc=yinghan@google.com \
/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.