Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
wiki:managing_resources_cpu_gpu [2020/03/03 13:31] – [Managing processing unit topologies] neyronwiki:managing_resources_cpu_gpu [2020/03/03 13:43] – [First scenario, simple] neyron
Line 68: Line 68:
  
 Also, if some nodes do not have any GPU, you could set the value of the property for the corresponding resources to ''gpudevice=-1'', and let the users add to the ''oarsub'' command a ''-p "gpudevice >=0"'' in order to get resources with GPUs. Also, if some nodes do not have any GPU, you could set the value of the property for the corresponding resources to ''gpudevice=-1'', and let the users add to the ''oarsub'' command a ''-p "gpudevice >=0"'' in order to get resources with GPUs.
 +
 +But be '''warned''', that the following commands will mostly not provide what a user would expect:
 +<code bash>
 +$ oarsub -l gpudevice=1 
 +</code>
 +will gives all resources matching one identifier of gpudevices, which means all nodes limited to their first gpus (''gpudevice=0''), or second gpus (''gpudevice=1''), or all nodes which have no gpus (''gpudevice=-1'').
 +
 +<code bash>
 +$ oarsub -l gpudevice=N
 +</code>
 +with N > 1 makes even less sense. See the setup proposed in the section below if you want to let your users request N gpus like that (using ''oarsub -l gpu=N'').
 +
 +
 +
 +
 +
  
 ===== Second scenario, more complex ===== ===== Second scenario, more complex =====
wiki/managing_resources_cpu_gpu.txt · Last modified: 2020/03/03 14:10 by neyron
Recent changes RSS feed GNU Free Documentation License 1.3 Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki