hi,
please always copy the list.
yes, this looks like you are getting the same behavior that i've seen earlier.
i have not looked into the code, but it might be that the fix GPU is ignoring
the offset or GPU index range parameter.
mike,
it also would be more flexible to handle this in a similar way as NAMD does it,
i.e. have single string that is then turned into a list, e.g. 0,1,2,3
or 0-3 or 1,3,2,4,
the latter is which is what i need for our 4-GPU nodes to get the best GPU to
processor mapping (since our machines have two southbridges, and you want
to tie the GPUs to the processor that hosts the southbridge where the individual
GPU is attached to).
cheers,
axel.
2011/3/15 Yangpeng Ou <[email protected]...>: