Just for my own sake, I'm calling every "memory pool"/zone/"resource group" a container here.

Requirements

• A container must have some limit on the amount of memory it may use.
  • Limits must apply to unmapped page cache, anonymous memory, and shared memory.
  • "Use" can be easily determined by the allocating container. It is harder to determine which container is _currently_ or most actively using a page.
• The overhead in storage, processing time, and dedicated lines of code to the greater kernel should be minimized
• Memory which is private to the container (say, anonymous memory) must be strictly accounted to that container

Icing on the Cake

• Limits would be nice to have on kernel structures
• Overcommitting memory should be allowed. We should not allow memory on a system to go completely unused.
• Memory for files may be accounted to either the container or a shared pool
  • Some care should be taken to ensure that a container may not abuse this shared pool
  • It is preferable to actually determine when sharing is "actually" occurring, but approximate metrics should be OK. This requirement is very secondary to any overhead which it might exhibit.
• Should allow runtime flexibility in size and number of containers
  • We should be able to change limits easily
  • We should be able to create and destroy them easily to satisfy the needs of application containers (not all containers are long-lived)
• A task might want to change containers at runtime. This might be a database or web server which wants to "do work" for a particular set of users, but doesn't want to go through the overhead of starting a whole new instance.

Software Zones

Use the existing Linux zone model to create sets of contiguous memory. Each of these is a subset of a current 'struct zone'. Each container gets one or more of these zones from which to allocate its pages. Pages shared between containers will be placed in centralized, "shared" zones.

This code's use of the existing Linux structures would let it do things like page reclaim with the existing algorithms.

Static Page Ownership (the classic CKRM way among others)

Add a pointer to 'struct page', and point it to an object that represents the container which caused the page's allocation. Don't change this until the page gets freed. Any other users of this page don't get charged for it.

Partial Page Ownership (Beancounters????)

Make sure that any additional users get charged, even if they are not the "first" user. Multiple users in a single container should not be charged multiple times. Overhead of figuring this out exactly could be more costly than other approaches.