Add the swapMemorySupport requirement to OOM tests
Add the swapMemorySupport requirement to all tests related to the OOM killer. The --memory option has the subtle side effect of defaulting --memory-swap to double the value of --memory. The OOM killer doesn't kick in until the container exhausts memory+swap, and so without the memory swap cgroup the tests will timeout due to swap being effectively unlimited. Document the default behavior of --memory-swap in the docker run man page. Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
This commit is contained in:
parent
0d227954c5
commit
ab42b091ee
@ -353,7 +353,8 @@ as memory limit.
|
|||||||
**--memory-swap**="LIMIT"
|
**--memory-swap**="LIMIT"
|
||||||
A limit value equal to memory plus swap. Must be used with the **-m**
|
A limit value equal to memory plus swap. Must be used with the **-m**
|
||||||
(**--memory**) flag. The swap `LIMIT` should always be larger than **-m**
|
(**--memory**) flag. The swap `LIMIT` should always be larger than **-m**
|
||||||
(**--memory**) value.
|
(**--memory**) value. By default, the swap `LIMIT` will be set to double
|
||||||
|
the value of --memory.
|
||||||
|
|
||||||
The format of `LIMIT` is `<number>[<unit>]`. Unit can be `b` (bytes),
|
The format of `LIMIT` is `<number>[<unit>]`. Unit can be `b` (bytes),
|
||||||
`k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you don't specify a
|
`k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you don't specify a
|
||||||
|
Loading…
x
Reference in New Issue
Block a user