Date: Sat, 14 Aug 2004 23:53:22 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/cam/scsi scsi_target.c src/sys/dev/mii mii.c src/sys/fs/fifofs fifo_vnops.c src/sys/gnu/ext2fs ext2_vnops.c src/sys/kern init_main.c kern_conf.c kern_descrip.c kern_event.c kern_exec.c kern_exit.c kern_fork.c kern_sig.c sys_pipe.c tty.c ... Message-ID: <20040815065322.GM991@funkthat.com> In-Reply-To: <200408150624.i7F6OhhR074096@repoman.freebsd.org> References: <200408150624.i7F6OhhR074096@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John-Mark Gurney wrote this message on Sun, Aug 15, 2004 at 06:24 +0000:
> jmg 2004-08-15 06:24:43 UTC
[...]
> Log:
> Add locking to the kqueue subsystem. This also makes the kqueue subsystem
> a more complete subsystem, and removes the knowlege of how things are
> implemented from the drivers. Include locking around filter ops, so a
> module like aio will know when not to be unloaded if there are outstanding
> knotes using it's filter ops.
>
> Currently, it uses the MTX_DUPOK even though it is not always safe to
> aquire duplicate locks. Witness currently doesn't support the ability
> to discover if a dup lock is ok (in some cases).
>
> Reviewed by: green, rwatson (both earlier versions)
With this change, kqueue enable make better work. (I've done a number
of buildworlds w/ it.) I'll enable it in a few days w/ a warning in
UPDATING about the effects of upgrading from a too old current.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040815065322.GM991>