Xiaochen Shen 2549545df5 intelrdt: always init IntelRdtManager if Intel RDT is enabled ... In current implementation: Either Intel RDT is not enabled by hardware and kernel, or intelRdt is not specified in original config, we don't init IntelRdtManager in the container to handle intelrdt constraint. It is a tradeoff that Intel RDT has hardware limitation to support only limited number of groups. This patch makes a minor change to support update command: Whether or not intelRdt is specified in config, we always init IntelRdtManager in the container if Intel RDT is enabled. If intelRdt is not specified in original config, we just don't Apply() to create intelrdt group or attach tasks for this container. In update command, we could re-enable through IntelRdtManager.Apply() and then update intelrdt constraint. Signed-off-by: Xiaochen Shen <xiaochen.shen@intel.com>		2017-09-20 01:37:31 +08:00
..
intelrdt.go	intelrdt: always init IntelRdtManager if Intel RDT is enabled	2017-09-20 01:37:31 +08:00
intelrdt_test.go	libcontainer: intelrdt: use init() to avoid race condition	2017-09-08 17:15:31 +08:00
stats.go	libcontainer: add support for Intel RDT/CAT in runc	2017-09-01 14:26:33 +08:00
util_test.go	libcontainer: add test cases for Intel RDT/CAT	2017-09-01 14:35:40 +08:00