OpenVZ Forum


Home » Mailing lists » Devel » A consideration on memory controller.
Re: A consideration on memory controller. [message #26308 is a reply to message #26307] Mon, 21 January 2008 10:22 Go to previous message
KAMEZAWA Hiroyuki is currently offline  KAMEZAWA Hiroyuki
Messages: 463
Registered: September 2006
Senior Member
On Mon, 21 Jan 2008 15:20:36 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:

> > > This topic needs more discussion, we have some form of page-cache
> > > control built into the memory controller.
> > > 
> > Hmm. ok. I'looking forward to see.
> > 
> 
> Could you elaborate on what sort of page-cache control you need, is it
> global page-cache control?
> 
What I mentioned to in my mail was global page cache. 

But, my purpose is isolate workload between applications and guarantee
stable performance/latency and memory controller's limiting page usage
feature will do half of work.
So, per-cgroup page-cache control is (maybe) good enough for making applications
stable by keeping room for immediate use of anon and by avoiding unnecessary swapout.

but above can be archieved by
 - reserve/guarantee amount of free memory by some technique, bacground 
   kthread, throttling,
 - do good design of swappiness.
 - etc...

So, the word "limiting page cache" itself is not important. Above will
limit amount of page-cache as a result.
Ways to reach my goal is not one, maybe. I should find the best one :)

Thanks,
-Kame

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH 0/4] Devices accessibility control group (v2)
Next Topic: [PATCH] An attempt to have an unlimitedly extendable sys_clone
Goto Forum:
  


Current Time: Fri Aug 29 07:55:50 GMT 2025

Total time taken to generate the page: 0.06411 seconds