[lkml]   [2011]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] sched/kthread: Complain loudly when others violate our flags
On Thu, 2011-09-29 at 20:55 -0700, Tejun Heo wrote:
> On Tue, Sep 27, 2011 at 05:17:34PM -0400, Steven Rostedt wrote:
> > For convenience and optimization, we are going to use the task's flag
> > PF_THREAD_BOUND as a way to know if a task is bound to a CPU or not. As
> > that is what the flag means.
> And I'm not sure this is a very good idea. Until now, PF_THREAD_BOUND
> meant "this task is explicitly bound to the current affinity (whatever
> it is) and thus it shouldn't be manipulated by third party".

That's exactly what we want it to mean. Not manipulated by workqueue or
anyone else. We don't plan on setting this flag if a task just happens
to have only one CPU in its affinity. We only set this flag if the task
is bounded to a CPU for good. When we see this flag set, we can therefor
assume that it will not migrate!

> The
> suggested change makes the flag much less orthogonal and useful. How
> much of convenience and optimization are we talking about?

Enough to not have to manually pin the task to the cpu at every lock.

-- Steve

 \ /
  Last update: 2011-09-30 06:11    [W:0.085 / U:6.516 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site