Linux Container Development
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	ckrm-tech-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Resource Management development plans
Date: Fri, 20 Jul 2007 21:49:39 +0530	[thread overview]
Message-ID: <20070720161939.GQ2216@linux.vnet.ibm.com> (raw)

Here's a tentative development plan on resource management from our side.
Would request others to comment/add their plans as part of this discussion.

This plan, alongwith appropriate usage scenarios, is being requested for 
kernel-summit discussion. Most likely, the resource management plans
will be presented as part of container discussion.

1. Infrastructure
	Userland interface for task-grouping, specifying group usage limits etc

	Paul Menage's container patches will be the basis for this
	infrastructure.

2. cpu controller

- Atleast 1-level deep hierarchical proportional fair-share scheduling
- Soft and Hard limit cpu usage of group
- Fine grained cpu control (ex: parts per 1000?)
- SCHED_FIFO policy for groups
        Groups having this policy will recv all cpu cycles as long
        as they have any task runnable. This is at the cost of 
	starving other non-SCHED_FIFO groups.
- Sleeper fairness - Will help bursty workloads
- Accounting - group cpu usage

3. memory controller

- Basic rss controller
- user space oom handler
- Improve shared page accounting
- Handling of soft limits
- Provide support for accounting kernel/user memory, slabs, page tables,
  dcache entries, vma's, etc
- Improved statistics (folding)
- Add support for better tuning of containers
        i.  Low and high water marks per container
        ii. Per container swappiness support
- Per container swap file(s)

4. Disk io controller

[I don't have sufficient details at the moment on disk io controller
requirements. Will add after I talk to relevant groups here]

	

	
-- 
Regards,
vatsa

                 reply	other threads:[~2007-07-20 16:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070720161939.GQ2216@linux.vnet.ibm.com \
    --to=vatsa-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=ckrm-tech-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    /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