On Tue, 26 Nov 2002, Terry Lambert wrote:
Uh, how exactly is that less obnoxious, given it's the same code
with a different name and an obnoxious inline instead of a macro?
8-).
it's shorter ..
You can always get from a thread to a single process but the reverse
always presents
Julian Elischer wrote:
The answer is that the code doesn't care what thread; it would
prefer to not have to think in terms of threads at all, but if
you want to force it to, then it's going to think in terms of
blocking contexts for the benefit of FreeBSD code it calls,
and nothing else.
As the person who broke it I'd like to help.. The problem was that it
referenced teh proc structure all over the place in several different
ways, and it was not obvious, without knowing the protocol which should
become thread references and which should stay proc references.
On Fri, 22 Nov 2002,
