OpenVZ Forum


Home » Mailing lists » Devel » containers development plans
Re: [ckrm-tech] containers development plans [message #14762 is a reply to message #14761] Tue, 10 July 2007 06:19 Go to previous messageGo to previous message
Paul Menage is currently offline  Paul Menage
Messages: 642
Registered: September 2006
Senior Member
On 7/9/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > - splitting the memory and cpu isolation parts of cpusets into two
> > separate subsystems (still backwards-compatible)
>
> I see memory isolation using cpusets as very topology dependent
> and I am not sure if the model would work for memory controllers.

I wasn't suggesting making any changes to the page-based memory
controllers as part of this.

Currently in the mainline kernel, the cpumask and nodemask portions of
cpusets are essentially two mostly-independent modules that happen to
be coupled together in the same file and use the same process tracking
system (cpusets). Once we have generic process containers, splitting
this into a "cpusets" subsystem that handles all the cpumask portions
of the existing cpusets, and a "memsets" subsystem that handles all
the nodemask and memory migration portions would remove that coupling
and give more flexibility.

Paul
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: [RFC][-mm PATCH 2/8] Memory controller containers setup (v3)
Next Topic: containers development plans (July 20 version)
Goto Forum:
  


Current Time: Fri Aug 16 03:04:28 GMT 2024

Total time taken to generate the page: 0.02919 seconds