[torquedev] Quick test report of cpuset support
garrick at usc.edu
Sat Feb 16 01:17:26 MST 2008
On Sat, Feb 16, 2008 at 05:15:38PM +1100, Chris Samuel alleged:
> The reason the vnode sets end up with no cpus allocated
> to them is because when you create the vnode sets the
> write to add the cpu is getting EPERM because the cpu
> has not yet been assigned to the jobset.
That sounds like a pretty dumb mistake on my part.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20080216/8503307d/attachment.bin
More information about the torquedev