From owner-freebsd-arch Sun May 19 15:14:31 2002 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3D15437B40C; Sun, 19 May 2002 15:14:29 -0700 (PDT) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.3/8.9.1) with ESMTP id g4JMEThU081621; Sun, 19 May 2002 15:14:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.3/8.12.3/Submit) id g4JMETM0081620; Sun, 19 May 2002 15:14:29 -0700 (PDT) Date: Sun, 19 May 2002 15:14:29 -0700 (PDT) From: Matthew Dillon Message-Id: <200205192214.g4JMETM0081620@apollo.backplane.com> To: Poul-Henning Kamp Cc: arch@FreeBSD.ORG Subject: Re: Marking deGianted functions ? References: <7119.1021845059@critter.freebsd.dk> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG fgrep MPSAFE */*.c. The convention is: /* * (other comments) * MPSAFE */ -Matt Matthew Dillon :Do we have a convention for marking functions which have been deGianted() ? : :If not, could we make some kind of comment convention so people can :determine the liberated parts ? as more and more parts of the kernel :gets out from under giant this becomes more and more of an issue. : :I realize that marking the non-safe entrypoints is the "logical" thing :to do, but probably less practical, or ? : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 :phk@FreeBSD.ORG | TCP/IP since RFC 956 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message