OpenVZ Forum


Home » Mailing lists » Devel » containers development plans (July 10 version)
Re: containers development plans (July 10 version) [message #14796 is a reply to message #14793] Wed, 11 July 2007 06:06 Go to previous messageGo to previous message
Paul Menage is currently offline  Paul Menage
Messages: 642
Registered: September 2006
Senior Member
On 7/10/07, Serge E. Hallyn <serge@hallyn.com> wrote:
>
> A (still under construction) list of features we expect to be worked on
> next year looks like this:
> 4. task containers functionality
> specific containers

A couple of more container subsystem requests that have come out of
the Linux Foundation Japan symposium, although I think they've also
been mentioned before more than once - per-container swap and disk I/O
scheduling.

I'm not familiar enough with the current Linux disk scheduler code to
know how easy/hard it is to add rate guarantees on a per-container
basis, but the swap one should be easier.

One potential issue with the swap container is how integrated should
it be with the memory controller? I can certainly see people wanting
to be able to use a swap controller without requiring a page-based
memory controller (e.g. you might want to combine it with node-based
control via cpusets instead) but adding two pointers to the mm_struct,
one for swap controller subsystem and one for memory controller
subsystem, seems a little bit ugly.

Paul

Report message to a moderator

[Message index]
 
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: [PATCH 1/6] Define and use task_active_pid_ns() wrapper
Next Topic: [PATCH 2/6] Rename pid_nr function
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Jul 08 22:18:24 GMT 2026

Total time taken to generate the page: 0.32213 seconds
Powered by FUDforum Powered by Virtuozzo Containers