Difference between revisions of "Containers/UBC discussion"
| Line 12: | Line 12: | ||
; what is implied by the term "guarantee" | ; what is implied by the term "guarantee" | ||
| − | # container will be able to touch that number of pages | + | # container will be able to touch that number of pages - I think this one (Hansendc) |
# container will be able to map that number of pages | # container will be able to map that number of pages | ||
# container will not be killed unless it touches that number of pages | # container will not be killed unless it touches that number of pages | ||
# anything else | # anything else | ||
Revision as of 15:45, 8 September 2006
- unified interface for mem, cpu, disk I/O
- It is still not clear whether we need unified interface.
- memory reclamation
- Pending to be implemented on top of BC.
- moving tasks across beancounters
- Required changes:
- saving bc on vma instead of mm
- can two threads in a process be in different BC contexts?
- changing mm->bc in set_bc_id().
- what is implied by the term "guarantee"
- container will be able to touch that number of pages - I think this one (Hansendc)
- container will be able to map that number of pages
- container will not be killed unless it touches that number of pages
- anything else
