From d8fd1da1d8c97f76553c867a37112b17a1924422 Mon Sep 17 00:00:00 2001 From: JamieWeider72 <147967555+JamieWeider72@users.noreply.github.com> Date: Tue, 16 Jul 2024 11:07:25 +0300 Subject: [PATCH 1/2] RUN-12616 new known limitation added --- docs/Researcher/scheduling/gpu-memory-swap.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/Researcher/scheduling/gpu-memory-swap.md b/docs/Researcher/scheduling/gpu-memory-swap.md index cb7e8e71fa..f920e3cc40 100644 --- a/docs/Researcher/scheduling/gpu-memory-swap.md +++ b/docs/Researcher/scheduling/gpu-memory-swap.md @@ -107,6 +107,7 @@ If you prefer your workloads not to be swapped into CPU memory, you can specify ## Known Limitations +* A pod created before the GPU memory swap feature was eneabled in that cluster is not able to be scheduled to a swap-enabled node. A proper event is generated in case no matching node is found. Users must re-submit those pods to make them swap-enabled. * GPU memory swap cannot be enabled if fairshare time-slicing or strict time-slicing is used, GPU memory swap can only be used with the default time-slicing mechanism. * CPU RAM size cannot be decreased once GPU memory swap is enabled. From 2f893b9dc067b3f8f9e85ddec3fe0458c35e7b10 Mon Sep 17 00:00:00 2001 From: JamieWeider72 <147967555+JamieWeider72@users.noreply.github.com> Date: Tue, 16 Jul 2024 11:34:19 +0300 Subject: [PATCH 2/2] RUN-12616 Added new known limitation --- docs/Researcher/scheduling/gpu-memory-swap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Researcher/scheduling/gpu-memory-swap.md b/docs/Researcher/scheduling/gpu-memory-swap.md index f920e3cc40..8ab1329954 100644 --- a/docs/Researcher/scheduling/gpu-memory-swap.md +++ b/docs/Researcher/scheduling/gpu-memory-swap.md @@ -107,7 +107,7 @@ If you prefer your workloads not to be swapped into CPU memory, you can specify ## Known Limitations -* A pod created before the GPU memory swap feature was eneabled in that cluster is not able to be scheduled to a swap-enabled node. A proper event is generated in case no matching node is found. Users must re-submit those pods to make them swap-enabled. +* A pod created before the GPU memory swap feature was eneabled in that cluster, cannot be scheduled to a swap-enabled node. A proper event is generated in case no matching node is found. Users must re-submit those pods to make them swap-enabled. * GPU memory swap cannot be enabled if fairshare time-slicing or strict time-slicing is used, GPU memory swap can only be used with the default time-slicing mechanism. * CPU RAM size cannot be decreased once GPU memory swap is enabled.