On Mon, 26 Jun 2000, Matthew Dillon wrote:
> This whole p vs curproc thing is a huge mess. 95% of the time
> p == curproc. The only places where it might not is in I/O ops
> that are completed by an interrupt or (in the case of NFS) some
> other process.
Any chances to clean this up ? Eg., change the policy to either
pass p as parameter or use curproc, but not both. As example of curproc/p
mess I can point to VFS_ROOT() call which misses p parameter, but
obviously needs it.
--
Boris Popov
http://www.butya.kz/~bp/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
