Editing Containers/Mini-summit 2008

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
There was a containers mini-summit at the [http://www.linuxsymposium.org/2008/ OLS'08]. This page served for organizing this event.
+
There will be a containers mini-summit at the [http://www.linuxsymposium.org/2008/ OLS'08]. This page is for organizing this mini-summit. Feel free to edit.
  
 
'''When''': 22nd of July 2008, 8:30-16:30<br/>
 
'''When''': 22nd of July 2008, 8:30-16:30<br/>
 
'''Where''': Ottawa, ON, Canada, Novotel Hotel (Albion A).
 
'''Where''': Ottawa, ON, Canada, Novotel Hotel (Albion A).
 
== Notes ==
 
 
For the notes from the mini-summit, '''see [[Containers/Mini-summit 2008 notes]].'''
 
  
 
== Proposal ==
 
== Proposal ==
  
The mini-summit proposal sent to OLS organizers; '''see [[/Proposal|proposal]]'''.
+
The mini-summit proposal sent to OLS organizers. '''See [[/Proposal|proposal]]'''.
  
 
== Topics to discuss ==
 
== Topics to discuss ==
Line 63: Line 59:
 
# Gyuil Cha
 
# Gyuil Cha
 
# YoungHo Kim
 
# YoungHo Kim
# Rob Woolley
 
# Daniel Robbins
 
# Jason Baron
 
# Subrata Modak
 
# Veerendra C
 
# Joe MacDonald
 
# Andrew Theurer
 
# Myron Stowe
 
# Peter Teoh
 
# Ricky Liang
 
 
</div>
 
</div>
  
Line 93: Line 79:
 
* Cgroups+Resource management  (11:30-2pm)
 
* Cgroups+Resource management  (11:30-2pm)
 
** Cgroup implementation
 
** Cgroup implementation
*** Locking (don't let cgroup_lock() become the BKL)
 
*** Transactional attachment
 
*** "procs" file
 
*** User-space notification API
 
**** Resource counter hit soft/hard limit
 
**** Task entered/left cgroup
 
**** OOM occurred
 
*** Binary statistics API
 
** Existing cgroups
 
*** Memory (Balbir's NOTE: I would prefer to take some of this discussion to my memory controller BoF on Wednesday. Lets discuss this at the end)
 
**** Supporting over-commit and guarantees
 
**** Soft-limits
 
**** Hierarchical borrowing - in kernel or userspace?
 
**** Per-cgroup refault information?
 
*** Kernel memory
 
*** Device
 
*** Memrlimit
 
**** Some push-back over this - can we give real use cases?
 
*** CPU scheduler
 
 
** Additional cgroups and their design
 
** Additional cgroups and their design
*** Swap (separate subsystem or merge with memory?)
 
*** Disk I/O (several proposed designs)
 
*** Network traffic classification
 
*** Freezer
 
*** Signaller
 
*** OOM Handler
 
 
** libcg - userspace explotation of control groups/resource management
 
** libcg - userspace explotation of control groups/resource management
*** Overview so far
+
** Resource management
*** Is kernel-based reclassification needed?
 
*** Real use-cases
 
*** Future directions
 
 
 
  
 
* Checkpoint/Restart  (2:30pm-5pm)
 
* Checkpoint/Restart  (2:30pm-5pm)

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)