linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* Re: memcg cgroup controller & sbrk interaction
       [not found] <1339118347.78794.YahooMailNeo@web112018.mail.gq1.yahoo.com>
@ 2012-06-08 14:51 ` Michal Hocko
  0 siblings, 0 replies; only message in thread
From: Michal Hocko @ 2012-06-08 14:51 UTC (permalink / raw)
  To: Ron Chen; +Cc: Linux Mailing List, linux-mm, cgroups mailinglist

On Thu 07-06-12 18:19:07, Ron Chen wrote:
[...]
> However, not only us, but others have found that the memcg controller
> does not cause sbrk(2) or mmap(2) to return error when the cgroup is
> under high memory pressure.

Yes, because memory controller tracks the allocated memory (with page
granularity) rather than address space. So the memory is accounted when
it is faulted in.

> Further, when the amount of free memory is really low, the Linux
> Kernel OOM killer picks something and kills it.

Yes, this is the result of the design when the memory is tracked during
page faults.

> http://www.spinics.net/lists/cgroups/msg02622.html
> 
> 
> We also would like to see if it is technically possible for the
> Virtual Memory Manager to interact with the memory controller
> properly and give us the semantics of setrlimit(2).

What prevents you from using setrlimit from inside the group?

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

--
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>

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2012-06-08 14:51 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1339118347.78794.YahooMailNeo@web112018.mail.gq1.yahoo.com>
2012-06-08 14:51 ` memcg cgroup controller & sbrk interaction Michal Hocko

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox