Note that a job may acquire more than one of the "chunks" implied by the above policy.  Again, assume the slot has 4096MB of memory, for an initial slot weight of 4.  Suppose a job acquires 2048MB of that memory.  Then the match will reduce the partitionable slot's weight from 4 to 2, for a match cost of 4-2=2.  The submitter's usage will increase by 2.
 
+{subsubsection: concurrency limits and accounting groups}
+Consumption Policies and negotiator p-slot splitting properly respect both accounting group quotas and concurrency limits.
+
 {section: Heterogeneous Resource Models}
 Consumption Policies are configurable on a per-slot basis, which makes it straightforward to support multiple resource consumption models on a single pool.