On Thu, Mar 16, 2006 at 08:38:36AM -0800, Paul Jackson wrote:
> While you created a subcpuset 'a', you changed the
> cpus and cpu_exclusive in the root cpuset. This
> changed -all- tasks to only be allowed to run on
> cpu 7.
oops sorry ..i did mean to say that i was trying to change
cpu-exclusive flag of a (and not the root cpuset).
>
> I'd guess you have some kernel thread or such that
> really, really wants to run on some other cpu.
>
> When I read you transcript, I expected it to say:
>
> # mkdir /dev/cpuset
> # mount -t cpuset cpuset /dev/cpuset # s/none/cpuset/ - clearer
> # cd /dev/cpuset
> # mkdir a
> # cd a # the missing step
Yes ..you are right. I did run 'cd a' and then ran the below commands.
> # /bin/echo 7 > cpus
> # /bin/echo 1 > cpu_exclusive
> When I do your commands (without the 'cd a'), I don't
> see any problem or hang on my Altix test box. But that
> probably just means I am not critically depending at that
> moment on some kernel thread running on any particular cpu.
Did you try with the 'cd a' (in other words turn on exclusive
property of cpuset 'a')?
--
Regards,
vatsa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
