Date: Wed, 14 Nov 2001 15:31:28 -0800 From: "Glenn Gombert" <glenngombert@onebox.com> To: current@FreeBSD.ORG Subject: Re: RE: lock order reversal for today's -CURRENT Message-ID: <20011114233128.VSPB29441.mta11.onebox.com@onebox.com>
next in thread | raw e-mail | index | archive | help
Is there a good , current description of how & why the various mutexe's & conditon variables are used for somewhere?? I see what they are doing in the code, but would like to get the big picture of why they are used in one place (and not another type).. Thanks, Glenn G. > I'm not against the concept of multiple pools, but I'm not really > for it either. The various mutexes are already far too complex > for their own good... look at SX locks, for example. The > struct sx is about 8 times as big as it needs to be to implement > reasonable functionality. I would scrap the upgrade and > downgrade API and I would scrap the condition variables > and go with a simple shared/exclusive counter. > > -Matt > Matthew Dillon > <dillon@backplane.com> > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011114233128.VSPB29441.mta11.onebox.com>