Srivatsa wrote:
> That again is not fool-proof. What if kernel-tasks change their cpu affinity
> after we have done the is_pinned_kernel_thread() test? Ideally they
> should not, but one never knows!
>
> IMHO we simply should not allow kernel threads to move out of top-cpuset
Well ... in some
On Thu, Jun 21, 2007 at 10:51:52AM -0700, Paul Jackson wrote:
> The only problem comes with kernel tasks that are pinned to less than
> the entire system, and that are in the top cpuset.
That again is not fool-proof. What if kernel-tasks change their cpu affinity
after we have done the
On Thu, Jun 21, 2007 at 10:51:52AM -0700, Paul Jackson wrote:
The only problem comes with kernel tasks that are pinned to less than
the entire system, and that are in the top cpuset.
That again is not fool-proof. What if kernel-tasks change their cpu affinity
after we have done the
Srivatsa wrote:
That again is not fool-proof. What if kernel-tasks change their cpu affinity
after we have done the is_pinned_kernel_thread() test? Ideally they
should not, but one never knows!
IMHO we simply should not allow kernel threads to move out of top-cpuset
Well ... in some
> Yeah .."allow movement if it doesn't result in changing kernel-threads's cpu
> affinity" sounds good, except it is hard to implement in cpuset's
> context I think. For ex: we now have to take additional steps when
> changing 'cpus_allowed' of a cpuset such that it doesn't violate any cpu
>
On Thu, Jun 21, 2007 at 10:07:12AM -0700, Paul Jackson wrote:
> Ingo, responding to Srivatsa:
> > > Or maybe allow movement if it
> > > doesn't result in changing kernel-threads's cpu affinity.
> >
> > yeah, i'd agree ..
>
> Good point. I'd agree too.
Yeah .."allow movement if it doesn't
Ingo, responding to Srivatsa:
> > Or maybe allow movement if it
> > doesn't result in changing kernel-threads's cpu affinity.
>
> yeah, i'd agree ..
Good point. I'd agree too.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
* Srivatsa Vaddagiri <[EMAIL PROTECTED]> wrote:
> But I am wondering if attach_task() should leave kernel threads alone
> and act only upon user-space threads. Or maybe allow movement if it
> doesn't result in changing kernel-threads's cpu affinity.
yeah, i'd agree with the latter. We could
* Srivatsa Vaddagiri [EMAIL PROTECTED] wrote:
But I am wondering if attach_task() should leave kernel threads alone
and act only upon user-space threads. Or maybe allow movement if it
doesn't result in changing kernel-threads's cpu affinity.
yeah, i'd agree with the latter. We could also
Ingo, responding to Srivatsa:
Or maybe allow movement if it
doesn't result in changing kernel-threads's cpu affinity.
yeah, i'd agree ..
Good point. I'd agree too.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
On Thu, Jun 21, 2007 at 10:07:12AM -0700, Paul Jackson wrote:
Ingo, responding to Srivatsa:
Or maybe allow movement if it
doesn't result in changing kernel-threads's cpu affinity.
yeah, i'd agree ..
Good point. I'd agree too.
Yeah ..allow movement if it doesn't result in changing
Yeah ..allow movement if it doesn't result in changing kernel-threads's cpu
affinity sounds good, except it is hard to implement in cpuset's
context I think. For ex: we now have to take additional steps when
changing 'cpus_allowed' of a cpuset such that it doesn't violate any cpu
affinity of
Srivatsa wrote:
# move all tasks from top cpuset to 'foo' cpuset
sed -nu p < /dev/cpuset/tasks > /dev/cpuset/foo/tasks
Aha - that won't work very well, as you noticed.
In looking through my past email archives, I can see where I have
recommended this trick to move things -into-
Paul,
You had once revealed a cute one-line command to move all tasks from
one cpuset to another [1], which was:
# move all tasks from top cpuset to 'foo' cpuset
sed -nu p < /dev/cpuset/tasks > /dev/cpuset/foo/tasks
I somewhat regret now having fallen for it and using it
Paul,
You had once revealed a cute one-line command to move all tasks from
one cpuset to another [1], which was:
# move all tasks from top cpuset to 'foo' cpuset
sed -nu p /dev/cpuset/tasks /dev/cpuset/foo/tasks
I somewhat regret now having fallen for it and using it
Srivatsa wrote:
# move all tasks from top cpuset to 'foo' cpuset
sed -nu p /dev/cpuset/tasks /dev/cpuset/foo/tasks
Aha - that won't work very well, as you noticed.
In looking through my past email archives, I can see where I have
recommended this trick to move things -into- the
16 matches
Mail list logo
