From owner-freebsd-current Fri Sep 22 21:56:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id A800237B422 for ; Fri, 22 Sep 2000 21:56:09 -0700 (PDT) Received: (qmail 11494 invoked by uid 666); 23 Sep 2000 04:56:05 -0000 Received: from unknown (HELO jules.elischer.org) (203.59.169.104) by mail.m.iinet.net.au with SMTP; 23 Sep 2000 04:56:05 -0000 Message-ID: <39CC37D4.167EB0E7@elischer.org> Date: Fri, 22 Sep 2000 21:55:48 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Bosko Milekic Cc: current@FreeBSD.ORG Subject: Re: Locking doc.? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bosko Milekic wrote: > > I don't believe so. There are several external resources, such as > on-line papers, and so on. There is also a man page (which I've found > from jasone's web space) which has been prepared by Sheldon Hearn and > which should be at ~jake/mutex.9 > As far "standard way to do it" documents - I haven't seen any and I'm > not sure how worthwile it would be to do this at this point in time, as > the code is still quite dynamic. > (Of course, I'm not implying "don't do it," just "be careful when you > do it" What I'm looking for is something that says for example, what stategy should be used for deadlock avoidance. For example. "Order of locking should be proc then vnode then socket then mbuf", or "Use asleep() await() to back out when encountering a locked item that stays locked for more than xx uSecs." At the moment there is no guide as to how one should combine locks in various different subsystems. Throwing a lock in every structure is one thing but then to tie the whole bundle up together is a completely different ballgame. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message