add runc shim support for sched core
In linux 5.14 and hopefully some backports, core scheduling allows processes to be co scheduled within the same domain on SMT enabled systems. The containerd impl sets the core sched domain when launching a shim. This allows a clean way for each shim(container/pod) to be in its own domain and any additional containers, (v2 pods) be be launched with the same domain as well as any exec'd process added to the container. kernel docs: https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/core-scheduling.html Signed-off-by: Michael Crosby <michael@thepasture.io>
This commit is contained in:
@@ -67,7 +67,9 @@ type Config struct {
|
||||
Timeouts map[string]string `toml:"timeouts"`
|
||||
// Imports are additional file path list to config files that can overwrite main config file fields
|
||||
Imports []string `toml:"imports"`
|
||||
|
||||
// OpenTelemetry configuration
|
||||
OpenTelemetry OpenTelemetryConfig `toml:"otel"`
|
||||
// StreamProcessors configuration
|
||||
StreamProcessors map[string]StreamProcessor `toml:"stream_processors"`
|
||||
}
|
||||
|
||||
@@ -165,6 +167,14 @@ type ProxyPlugin struct {
|
||||
Address string `toml:"address"`
|
||||
}
|
||||
|
||||
// OpenTelemetryConfig provides open telemetry configuration
|
||||
type OpenTelemetryConfig struct {
|
||||
ServiceName string `toml:"service_name"`
|
||||
ExporterName string `toml:"exporter_name"`
|
||||
ExporterEndpoint string `toml:"exporter_endpoint"`
|
||||
TraceSamplingRatio float64 `toml:"trace_sampling_ratio"`
|
||||
}
|
||||
|
||||
// BoltConfig defines the configuration values for the bolt plugin, which is
|
||||
// loaded here, rather than back registered in the metadata package.
|
||||
type BoltConfig struct {
|
||||
|
||||
Reference in New Issue
Block a user