Date: Thu, 25 Feb 1999 12:03:24 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Luoqi Chen <luoqi@watermarkgroup.com>, dfr@nlsystems.com, freebsd-hackers@FreeBSD.ORG, mjacob@feral.com Subject: Re: Panic in FFS/4.0 as of yesterday - update Message-ID: <199902252003.MAA08737@apollo.backplane.com> References: <199902231444.JAA02311@lor.watermarkgroup.com> <199902231848.KAA51270@apollo.backplane.com> <199902250916.BAA02250@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is very messy, so only hard-core kernel hackers should try this.
This should solve the getnewbuf problems, but it required some significant
rewriting to re-encapsulate the free/dirty/bufferspace accounting,
implement emergency reserves for the updateproc, and to fix NFS.
http://freefall.freebsd.org/~dillon/getnewbuf-diff.txt
This is not well tested yet. IT MAY BLOW UP YOUR MACHINE! However,
I think it is very close to ideal. If there are bugs, they are going
to be simple-stupid things rather then design issues.
This patch contains a bunch of other cruft from other things, but
mainly bug fixes. The size of struct buf also changes ( due to one
of the pieces of cruft ). I didn't want to strip this stuff out because
then it will not patch cleanly into -current for the people trying to
test the getnewbuf() problem. If you want, though, you can remove
the struct chain_info junk from the sys/buf.h portion of the patch. It's
part of the new VN device's direct-swap support ( not yet committed ).
-Matt
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?199902252003.MAA08737>