config-linux: add Intel RDT CLOS name sharing support #988
Conversation
Creating a dedicated RDT Class of Service (CLOS) for each running
container, even they have exactly same Scheam, will lead to short of
CLOS, since there is a hardware limit for the number of CLOS, around
16 CLOS per platform.
This PR add one parameter 'closID' into existed spec to allow user
to specify which RDT Class of Service (CLOS) the container will be
located. So it can place these containers with same Schema into one
single CLOS.
Example:
"linux": {
"intelRdt": {
"closID": "guaranteed_group",
"l3CacheSchema": "L3:0=ffff0;1=3ff"
}
}
Signed-off-by: Lin Yang <lin.a.yang@intel.com>
|
We could also call this "Intel RDT control group sharing between containers" feature which we have discussed in: For more information about Intel RDT CAT and MBA support in OCI: |
|
@crosbymichael @vishh Could you please help to review this design proposal of "Intel RDT control group sharing between containers" feature if you get chance? Thanks in advance. Really appreciated. |
|
@xiaochenshen does this look good to you? |
|
Yes, Intel RDT CLOS/group sharing between containers is a real user scenario for OCI and Intel RDT users. Intel RDT has hardware limit (num_closids) for RDT control groups. The number of the limit is exported by kernel through In current implementation of Intel RDT/CAT support for OCI (opencontainers/runc#433, opencontainers/runc#1279) and Intel RDT/MBA support for OCI (opencontainers/runc#1596, #932, opencontainers/runc#1632), we create new dedicated RDT group (CLOS) for each container which specified Intel RDT config in With this PR, we could mitigate the issue of running out of RDT CLOS. |
|
LGTM |
|
LGTM |
Previously, it will create a dedicated RDT Class of Service (CLOS) for each running container, even they have exactly same Scheam. This will lead to short of CLOS, since there is a hardware limit for the number of CLOS, around 16 CLOS per platform.
This PR add one parameter 'closID' into existed spec to allow user to specify which RDT Class of Service (CLOS) the container will be located. So it can place these containers with same Schema into one single CLOS.
Example:
Fixes: runc issue 1878
Co-authored with Dakshina Ilangovan @dakshinai