Containers/UBC discussion

unified interface for mem, cpu, disk I/O

It is still not clear whether we need unified interface.

Having one syscall for setting values for different resources seems OK if leaving alone the meaning of the "value" notion.

memory reclamation

Pending to be implemented on top of BC.

moving tasks across beancounters

Required changes:

1. saving bc on vma instead of mm
2. can two threads in a process be in different BC contexts?
3. changing mm->bc in set_bc_id().

what is implied by the term "guarantee"

1. container will be able to touch that number of pages - I think this one (Hansendc)
2. container will be able to map that number of pages
3. container will not be killed unless it touches that number of pages
4. anything else

make it possible to charge full user page to its allocator and keep it charged till unmapped