Description of problem:

Documentation for doc-Resource_Management_Guide does not detail interdependencies and ordering of memory subsystem values.

Version-Release number of selected component (if applicable): 1.0

Section 3.7 (sec-memory) Memory Subsystem

memory.limit_in_bytes
memory.memsw.limit_in_bytes

It needs to be noted that memory.memsw.limit_in_bytes can not be set without first setting memory.limit_in_bytes.

Also the order these are placed in cgconfig.conf is important (The reverse order to which you would set them on the command line).

e.g.
Example A: (VALID):
        memory {
                memory.limit_in_bytes = 40;
        }
Example B: (VALID):
        memory {
                memory.memsw.limit_in_bytes = 40;
                memory.limit_in_bytes = 40;
        }
Example C (INVALID):
        memory {
                memory.memsw.limit_in_bytes = 40;
        }
Example D (INVALID):
        memory {
                memory.limit_in_bytes = 40;
                memory.memsw.limit_in_bytes = 40;
        }


This is reproducible on the command line:
Trying to set a value just for memsw.limit_in_bytes
# /bin/echo 50 > /cgroup/memory/patrol/memory.memsw.limit_in_bytes
/bin/echo: write error: Invalid argument

Now correctly setting a value in limit_in_bytes first.
# /bin/echo 50 > /cgroup/memory/patrol/memory.limit_in_bytes
# /bin/echo 50 > /cgroup/memory/patrol/memory.memsw.limit_in_bytes