The rpc only reports one field, i.e. the cgroup driver, to kubelet. Containerd determines the effective cgroup driver by looking at all runtime handlers, starting from the default runtime handler (the rest in alphabetical order), and returning the cgroup driver setting of the first runtime handler that supports one. If no runtime handler supports cgroup driver (i.e. has a config option for it) containerd falls back to auto-detection, returning systemd if systemd is running and cgroupfs otherwise. This patch implements the CRI server side of Kubernetes KEP-4033: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4033-group-driver-detection-over-cri Signed-off-by: Markus Lehtonen <markus.lehtonen@intel.com>
17 lines
602 B
Go
17 lines
602 B
Go
package configs
|
|
|
|
type IntelRdt struct {
|
|
// The identity for RDT Class of Service
|
|
ClosID string `json:"closID,omitempty"`
|
|
|
|
// The schema for L3 cache id and capacity bitmask (CBM)
|
|
// Format: "L3:<cache_id0>=<cbm0>;<cache_id1>=<cbm1>;..."
|
|
L3CacheSchema string `json:"l3_cache_schema,omitempty"`
|
|
|
|
// The schema of memory bandwidth per L3 cache id
|
|
// Format: "MB:<cache_id0>=bandwidth0;<cache_id1>=bandwidth1;..."
|
|
// The unit of memory bandwidth is specified in "percentages" by
|
|
// default, and in "MBps" if MBA Software Controller is enabled.
|
|
MemBwSchema string `json:"memBwSchema,omitempty"`
|
|
}
|