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 the question "which thread?". This question can only be > > answered with external information or if you know there is only one > > thread at this moment. > > 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. Hense the confusion as to whether to use a thread or a proc.. > > Did you want me to update the patch to use your FIRST_THREAD_IN_PROC > macro and resend it? you could but the fact that FIRST_THREAD_IN_PROC() is used indicates that the whole thing is broken anyway. Your edits are mostly mechanical and don't actually solve the problem. To do that you probably need to actually rewrite some of it I think. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
