I guess the other thing missing, from my perspective, is the ability for
any process to be able to add to the watcher list of any task.
In Linux Job, this is when you say "I would like that certain process to be
part of a certain job container".
This might involve locking on the watcher list. As stated previously, Jack
Steiner doesn't agree with me here but it really is a need for the current
Job without removing functionality which may be in use.
It seems like (unless I'm reading wrong, which may be the case :) the watcher
list in Matt's example is only added too. When a module decides it
doesn't want to watch a task any more, it ignores it. That doesn't take
anything out of the watcher list, it just makes it so an entry in the list
points to NULL, right?
Is there a safe way to add to the end of the watcher list without locks?
Would locks be an option if we could show they don't cost much? Like I
said earlier in the discussions, I'm certainly not interested in making
Linux perform poorly and that issue takes precedent over anything else.
Erik