On Tue, 14 Feb 2017, William Hay wrote:
...
We tweak the permissions on the device nodes from a privileged prolog
but otherwise I suspect we're doing something similar.
Hi William,
Yeah, but I've put the permission tweaker in the starter, as that fits our
existing model a bit better (looking ahead to multi-node GPU codes in
future).
One thing to watch out for is that unless you disable it the device
driver can change the permissions on the device nodes behind your back.
The device driver, or do you mean any CUDA program at all?
It's a bit of an eye-opener to see no dev entries being created by the
kernel module / udev, then strace a simple CUDA program and watch it try
to mknod some /dev entries and call a privileged binary to do some
modprobe/mknod's before actually doing what the program's supposed to do.
Would really like to know how to stop it doing that: had been wondering
about offering the ability to reconfigure or reset the GPU card via a job
request / JSV / starter method, but at the moment I cannot run anything
interesting with root privs without screwing up permissions. Grr.
...
We have separate requests for memory, gpus ,local scratch space, etc
with sensible defaults. If someone did use the command line it could
end up looking quite like the example you give.
...
Do people fiddle with them and stick funny numbers in, resulting in GPUs
unintentionally left idle?
Some of the things I've seen in #$ lines - bleugh.
Cheers,
Mark
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
