Skip to content

Commit a6c310a

Browse files
committed
config-linux: clarify when the RDT sub-directory should be removed.
Signed-off-by: Ismo Puustinen <[email protected]>
1 parent b280c07 commit a6c310a

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

config-linux.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -770,6 +770,10 @@ The following rules on parameters MUST be applied:
770770

771771
* If `closID` is set, and none of `l3CacheSchema`, `memBwSchema` or `schemata` are set, runtime MUST check if corresponding pre-configured directory `closID` is present in mounted `resctrl`. If such pre-configured directory `closID` exists, runtime MUST assign container to this `closID` and [generate an error](runtime.md#errors) if directory does not exist.
772772

773+
* If `closID` is not set and the runtime has created the sub-directory, the runtime MUST remove the sub-directory when the container is deleted.
774+
775+
* If `closID` is set or the runtime has not created the sub-directory, the runtime MUST NOT remove the sub-directory when the container is deleted.
776+
773777
* If `enableMonitoring` is set, the runtime MUST create a dedicated MON group
774778
for the container. The runtime MUST use the container ID from
775779
[`start`](runtime.md#start) as the name of the MON group, i.e. create

0 commit comments

Comments
 (0)