Date: Mon, 1 Apr 2002 21:10:36 -0800 From: Jonathan Mini <mini@haikugeek.com> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: www/en/smp index.sgml Message-ID: <20020401211036.C68138@stylus.haikugeek.com> In-Reply-To: <200204020447.g324lZg60015@freefall.freebsd.org>; from rwatson@FreeBSD.ORG on Mon, Apr 01, 2002 at 08:47:35PM -0800 References: <200204020447.g324lZg60015@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson [rwatson@FreeBSD.ORG] wrote : > rwatson 2002/04/01 20:47:35 PST > > Modified files: > en/smp index.sgml > Log: > Document Jonathan Mini's sysctl locking work. I'm not sure I understand > exactly what MEMLOCK() protects, so there should really be more comments > in kern_sysctl.c. Once they're there, I'll update the task. > > Document Jake's addition of a userland tool to manage KTR event dumps. So: --- sys/kern/kern_sysctl.c,old Mon Apr 1 21:05:33 2002 +++ sys/kern/kern_sysctl.c Mon Apr 1 21:07:07 2002 @@ -59,7 +59,7 @@ static MALLOC_DEFINE(M_SYSCTLOID, "sysctloid", "sysctl dynamic oids"); /* - * Locking and stats + * Locking - this locks the sysctl tree in memory. */ static struct sx memlock; Perhaps it would be a better idea to change MEMLOCK() to something like SYSCTL_TREE_LOCK(), or perhaps just SYSCTL_LOCK(). It's only called MEMLOCK() because phk called the old lock "memlock," which is a pretty silly reason. > Revision Changes Path > 1.62 +16 -1 www/en/smp/index.sgml > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe cvs-all" in the body of the message -- Jonathan Mini mini@haikugeek.com <baka^ni> desolation... despair... plastic forks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020401211036.C68138>