Christoph wrote:
> Here is one approach to locking using xchg.
What I see here doesn't change the behaviour of the
kernel any - just adds some locked exchanges, right?
I thought the hard part was having some other task
change the current tasks mempolicy. For example,
how does one task sync another tasks mempolicy up
with its cpuset, or synchronously get the policies
zonelist or preferred node set correctly?
I guess that this approach is intended to show how
to make it easy to add that hard part, right?
... whatever ... guess I'm still missing something ...
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
