Date: Tue, 27 Jun 2000 06:45:45 +0700 (ALMST) From: Boris Popov <bp@butya.kz> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: John Polstra <jdp@polstra.com>, chris@calldei.com, hackers@FreeBSD.ORG Subject: Re: struct proc Message-ID: <Pine.BSF.4.10.10006270634460.51466-100000@lion.butya.kz> In-Reply-To: <200006262204.PAA30219@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10006270634460.51466-100000>