Date: Sat, 1 Feb 1997 17:58:35 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: joerg_wunsch@uriah.heep.sax.de Cc: mcgovern@spoon.beta.com, hackers@freebsd.org Subject: Re: Device driver help needed... Message-ID: <199702020058.RAA07122@phaeton.artisoft.com> In-Reply-To: <Mutt.19970202014250.j@uriah.heep.sax.de> from "J Wunsch" at Feb 2, 97 01:42:50 am
next in thread | previous in thread | raw e-mail | index | archive | help
> curproc is an ugly thing in an SMP environment, since there are > multiple current processes. Generic implementation strategy is to replace CURPROC with a macro. I believe the current SMP code references the curproc out of the processor specific data area, along with the kernel stack. It's really questionable whether this is a good idea, if we ever intend to support kernel multithreading. But as things stand now, you still use "curproc", and you get the right one for the CPU you are running on. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702020058.RAA07122>