You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 9, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/user/nvidia-dranet/index.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -265,7 +265,7 @@
265
265
</span></span></code></pre></div><p>The <code>ResourceClaimTemplate</code> allows to specify multiple devices, in this case 2
266
266
GPUs and 2 NICs and also apply a constraint so the NICs and the GPUs share the
267
267
same pcie root, avoiding the penalty of suboptimal topologies.</p><p>It is important to indicate that each Pod will obtain a <code>ResourceClaim</code> from the
268
-
<code>ResourceClaimTemplate</code>, and since your servers may be connected in a <ahref=https://docs.nvidia.com/networking/display/ibclusterbringupprocedure/setting+the+infiniband+cluster+topology>rail
268
+
<code>ResourceClaimTemplate</code>, and since your servers may be connected in a <ahref=https://docs.nvidia.com/networking/display/infinibandclusterbringupprocedure/setting+the+infiniband+cluster+topology>rail
269
269
optimized
270
270
architecture</a>,
271
271
the GPUs requested need to be also aligned across the different servers. In this
0 commit comments