lkml.org 
[lkml]   [2005]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 3/5] cpuset: change marker for relative numbering
Paul Jackson <pj@sgi.com> wrote:
>
> > Given that you're developing a library to do all this, why not do proper
> > locking in userspace and require that all cpuset updates go via the
> > library?
>
> The superficial reason why not is that I can't prevent someone from
> doing "echo pid > /dev/cpuset/tasks", moving a task to another cpuset
> even as that task in the middle of dorking with its cpusets. Not all
> cpuset operations will involve using my blessed library.

If someone modifies a library-managed cpuset via the backdoor then the
library (and its caller) are out of sync with reality _anyway_. Why does
an encounter with this very small race window worsen things?
-
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/

\
 
 \ /
  Last update: 2005-11-06 22:01    [W:0.082 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site