Re: Locking doc.?

2000-09-22 Thread Bosko Milekic
On Fri, 22 Sep 2000, Julian Elischer wrote: > Throwing a lock in every structure is > one > thing but then to tie the whole bundle up together is a completely > different ballgame. Yes, that's the hard part. It can be potentially dangerous to, for example, call the mbuf resource alloc

Re: Locking doc.?

2000-09-22 Thread Julian Elischer
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

Re: Locking doc.?

2000-09-22 Thread Bosko Milekic
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" docum

Re: Locking doc.?

2000-09-22 Thread Greg Lehey
On Friday, 22 September 2000 at 19:50:11 -0700, Julian Elischer wrote: > Do we have a document that descibes in great detail the > locking policy that the SMPng code should follow? > > I've seen several descriptionms as to how it might be done, > but I haven't seen a "Ok we've decided that this is

Locking doc.?

2000-09-22 Thread Julian Elischer
Do we have a document that descibes in great detail the locking policy that the SMPng code should follow? I've seen several descriptionms as to how it might be done, but I haven't seen a "Ok we've decided that this is the strategy we are using" document. -- __--_|\ Julian Elischer