From owner-freebsd-current@FreeBSD.ORG Tue Feb 8 01:48:36 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEAE816A4CE; Tue, 8 Feb 2005 01:48:36 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6484743D1F; Tue, 8 Feb 2005 01:48:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4E26351432; Mon, 7 Feb 2005 17:48:35 -0800 (PST) Date: Mon, 7 Feb 2005 17:48:35 -0800 From: Kris Kennaway To: ALeine Message-ID: <20050208014835.GA567@xor.obsecurity.org> References: <200502062247.j16Mlg0r041149@marlena.vvi.at> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <200502062247.j16Mlg0r041149@marlena.vvi.at> User-Agent: Mutt/1.4.2.1i cc: freebsd-hackers@freebsd.org cc: k-sasaki@ist.osaka-u.ac.jp cc: rwatson@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: FW: Call for comments: CoxR, a CVS/mail-lists/BTS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 01:48:37 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 06, 2005 at 02:47:42PM -0800, ALeine wrote: > rwatson@freebsd.org wrote:=20 >=20 > > I appreciate that not everyone is a fan of mutex synchronization, > > but "mutex hell" is a bit of an odd description: most bugs I see > > getting reported (and fixed) aren't even locking-related. They're > > generally a property of lack of testing exposure for more obscure > > features or edge cases that are hard to test for without a wide > > testing base, such as edge-case hardware, bugs associated with > > longer run times, or a recently introduced feature, etc. >=20 > Well, mutex hell is more of a humorous description, but unfortunately > it is not too far from what is becoming a reality. I believe that > the path the FreeBSD Project has taken with the 5.x branch (not only > in regard to mutex locking but in general) has made things far too > complex in ways that make even seasoned hardcore developers such as > yourself unwilling to touch certain subsystems because only one or > two people really understand that system well enough to introduce > only a few (instead of a few dozen) critical bugs when changing that > subsystem. Or do you want to tell me that you could go right in and > get the critical section related stuff sorted out on your own without > John Baldwin and Stephan Uphoff in order to get to merge your UMA > related changes? :-) [...] Consider not insulting the intelligence of the FreeBSD developers if you want them to ever help you again with your kernel newbie questions. That kind of trash-talking may be cool in other projects, but around here it's not going to win you friends. Kris --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCCBpzWry0BWjoQKURAvilAKCOQpK0IOV04tUrVHXg6Og44lHm6gCgmQQy FufOtDWz+FTCB6KehbR169U= =oQAQ -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--