Date: Fri, 05 Aug 2005 16:30:32 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: jhb@freebsd.org Cc: freebsd-hackers@freebsd.org, hselasky@c2i.net Subject: Re: How to do proper locking Message-ID: <20050805.163032.133432410.imp@bsdimp.com> In-Reply-To: <200508051329.14767.jhb@FreeBSD.org> References: <200508041415.56140.jhb@FreeBSD.org> <200508042253.34165.hselasky@c2i.net> <200508051329.14767.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200508051329.14767.jhb@FreeBSD.org>
John Baldwin <jhb@freebsd.org> writes:
: Maybe, but another thing you need to consider is "maintainenance" overhead.
: Device drivers, especially, should be the simplest parts of the kernel to
: implement because we want to minimize the potential for screw up in that
: area. Having to trust that the same code is going to be duplicated 40 or 50
: times without any errors versus having it done once in a centralized place
: where it breaks everyone if it is broken is just insane. Otherwise, we might
: as well go write the whole kernel in assembly so we can tweak every last bit
: out of it. :)
History has shown that when you have to rely on 50 copies of something
being done right, 48 of them will, in fact, have 49 different things
wrong with them.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050805.163032.133432410.imp>