From: Andrea Arcangeli <aarcange@redhat.com>
To: Pavel Emelyanov <xemul@parallels.com>
Cc: lsf@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>
Subject: Re: [Lsf] [LSF][MM] rough agenda for memcg.
Date: Thu, 31 Mar 2011 18:20:50 +0200 [thread overview]
Message-ID: <20110331162050.GI12265@random.random> (raw)
In-Reply-To: <4D944801.3020404@parallels.com>
On Thu, Mar 31, 2011 at 01:23:13PM +0400, Pavel Emelyanov wrote:
> > b) single LRU and per memcg zone->lru_lock.
> > I hear zone->lru_lock contention caused by memcg is a problem on Google servers.
> > Okay, please show data. (I've never seen it.)
> > Then, we need to discuss Pros. and Cons. of current design and need to consinder
> > how to improve it. I think Google and Michal have their own implementation.
> >
> > Current design of double-LRU is from the 1st inclusion of memcg to the kernel.
> > But I don't know that discussion was there. Balbir, could you explain the reason
> > of this design ? Then, we can go ahead, somewhere.
>
> I would like to take part in that and describe what we've done with LRU
> in OpenVZ in details.
Sounds good.
>
> > a) Kernel memory accounting.
>
> This one is very interesting to me.
I expected someone would have been interested into that...
> > f) vm_overcommit_memory should be supproted with memcg ?
> > (I remember there was a trial. But I think it should be done in other cgroup
> > as vmemory cgroup.)
>
> And this one too - I have an implementation of overcommit management
> in OpenVZ, I can describe one and discuss pros-n-cons.
Ok, so I've added you to the second half of "what's next".
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-31 16:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 2:01 [LSF][MM] rough agenda for memcg KAMEZAWA Hiroyuki
2011-03-31 5:52 ` Greg Thelen
2011-03-31 12:27 ` [Lsf] " Jan Kara
2011-03-31 6:01 ` Balbir Singh
2011-03-31 6:03 ` Ying Han
2011-03-31 9:15 ` Zhu Yanhai
2011-04-01 2:36 ` Michel Lespinasse
2011-03-31 9:23 ` [Lsf] " Pavel Emelyanov
2011-03-31 16:20 ` Andrea Arcangeli [this message]
2011-03-31 18:14 ` Ying Han
2011-03-31 19:00 ` Pavel Emelyanov
2011-03-31 19:16 ` Ying Han
2011-03-31 19:22 ` Ying Han
2011-03-31 15:59 ` Andrea Arcangeli
2011-03-31 20:06 ` Johannes Weiner
2011-04-01 3:18 ` Michel Lespinasse
2011-04-01 1:16 ` KAMEZAWA Hiroyuki
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=20110331162050.GI12265@random.random \
--to=aarcange@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lsf@lists.linux-foundation.org \
--cc=xemul@parallels.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 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).