Re: cpuset - question

[Paul Jackson <pj@sgi.com>]

JaniD++ wrote:
> [root@dy-xeon-1 cpus_0]# /bin/echo 1 > mems
> /bin/echo: write error: Numerical result out of range
> [root@dy-xeon-1 cpus_0]# echo 1 >mems
> [root@dy-xeon-1 cpus_0]# cat mems
> 
> [root@dy-xeon-1 cpus_0]# /bin/echo $$ > tasks
> /bin/echo: write error: No space left on device

I'm guessing you are on a multi-processor, with a single
memory node, not a NUMA system with multiple memory nodes.

Or, at least, your kernel was compiled for that (with the
CONFIG_NUMA option disabled).

The first echo above failed because you tried to set bit 1
in mems, but only bit 0 is valid (only one memory node).

The second echo failed too, but your shells (like most
shells) builtin echo didn't display the error.

The 'cat mems' command showed that mems was not yet set,
which is indeed the case.

The third and final echo above, into 'tasks' failed because
you can't attach a task to a cpuset that has no memory specified.

If you had done '/bin/echo 0 > mems', it would have worked
much better.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/