Hi there, On Friday 13 January 2006 14:44, Ingo Molnar wrote: > - it should stay a semaphore (if it's a genuine counting > semaphore) > > - or it should get converted to a completion (if it's used as > a completion) > > - or it should get converted to struct work (if it's used as a > workflow synchronizer). Could we get for each of these and a mutex: - description - common use case - small argument why this and nothing else should be used there This would help driver writers a lot deciding what to use when, I think. PS: After reading the Linux Kernel one could write a PhD thesis just containing explanations, examples and measurements of sychronization primitives, since Linux implements at least most of them AFAIK :-) Thanks & Regards Ingo Oeser
Attachment:
pgp4ILKMTZZhu.pgp
Description: PGP signature
- Follow-Ups:
- Re: [patch 00/62] sem2mutex: -V1
- From: Ingo Molnar <[email protected]>
- Re: [patch 00/62] sem2mutex: -V1
- References:
- [patch 00/62] sem2mutex: -V1
- From: Ingo Molnar <[email protected]>
- Re: [patch 00/62] sem2mutex: -V1
- From: Duncan Sands <[email protected]>
- Re: [patch 00/62] sem2mutex: -V1
- From: Ingo Molnar <[email protected]>
- [patch 00/62] sem2mutex: -V1
- Prev by Date: Re: [PATCHSET] block: fix PIO cache coherency bug
- Next by Date: Re: [PATCH] UEAGLE : add iso support and commestic stuff
- Previous by thread: Re: [patch 00/62] sem2mutex: -V1
- Next by thread: Re: [patch 00/62] sem2mutex: -V1
- Index(es):