From 031ee645902de37d43292f7b1d415c86baf4a544 Mon Sep 17 00:00:00 2001 From: Tuomas Katila Date: Wed, 13 Sep 2023 10:47:39 +0300 Subject: [PATCH 1/2] gpu/doc: Add Max Series support and a note about SR-IOV Signed-off-by: Tuomas Katila --- cmd/gpu_plugin/README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/cmd/gpu_plugin/README.md b/cmd/gpu_plugin/README.md index e5e80324b..f95739299 100644 --- a/cmd/gpu_plugin/README.md +++ b/cmd/gpu_plugin/README.md @@ -24,6 +24,7 @@ Table of Contents * [Verify Plugin Registration](#verify-plugin-registration) * [Testing and Demos](#testing-and-demos) * [Labels created by GPU plugin](#labels-created-by-gpu-plugin) +* [SR-IOV use with the plugin](#sr-iov-use-with-the-plugin) * [Issues with media workloads on multi-GPU setups](#issues-with-media-workloads-on-multi-gpu-setups) * [Workaround for QSV and VA-API](#workaround-for-qsv-and-va-api) @@ -31,7 +32,7 @@ Table of Contents ## Introduction Intel GPU plugin facilitates Kubernetes workload offloading by providing access to -discrete (including Intel® Data Center GPU Flex Series) and integrated Intel GPU devices +discrete (including Intel® Data Center GPU Flex & Max Series) and integrated Intel GPU devices supported by the host kernel. Use cases include, but are not limited to: @@ -344,6 +345,12 @@ The GPU plugin functionality can be verified by deploying an [OpenCL image](../. If installed with NFD and started with resource-management, plugin will export a set of labels for the node. For detailed info, see [labeling documentation](./labels.md). +## SR-IOV use with the plugin + +GPU plugin does __not__ setup SR-IOV. It has to be configured by the cluster admin. + +GPU plugin does however support provisioning Virtual Functions (VFs) to containers for a SR-IOV enabled GPU. When the plugin detects a GPU with SR-IOV VFs configured, it will only provision the VFs and leaves the PF device on the host. + ## Issues with media workloads on multi-GPU setups OneVPL media API, 3D and compute APIs provide device discovery From 5ca3df666ae23a4f898324aef3627d2c6f1b9494 Mon Sep 17 00:00:00 2001 From: Tuomas Katila Date: Wed, 13 Sep 2023 10:48:32 +0300 Subject: [PATCH 2/2] xpum-sidecar: update deployment yaml to a newer one Signed-off-by: Tuomas Katila --- deployments/xpumanager_sidecar/kustomization.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/deployments/xpumanager_sidecar/kustomization.yaml b/deployments/xpumanager_sidecar/kustomization.yaml index c4cf89af8..728397536 100644 --- a/deployments/xpumanager_sidecar/kustomization.yaml +++ b/deployments/xpumanager_sidecar/kustomization.yaml @@ -1,6 +1,5 @@ -# XeLink topology information is only available from >= 1.x.y release resources: -- https://raw.githubusercontent.com/intel/xpumanager/v1.2.0_golden/deployment/kubernetes/daemonset-intel-xpum.yaml +- https://raw.githubusercontent.com/intel/xpumanager/V1.2.18/deployment/kubernetes/daemonset-intel-xpum.yaml namespace: monitoring apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization