Re: [RFC] unify semaphore implementations

Benjamin LaHaise writes:

> There are at least two users who need asynchronous semaphore/mutex 
> operations: aio_write (which needs to acquire i_sem), and nfs.  

What do you mean by asynchronous semaphore/mutex operations?  Are you
talking about a down operation that will acquire the semaphore if it
is free, but if not, arrange for a callback and return immediately, or
something?

Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [RFC] unify semaphore implementations
    • From: Benjamin LaHaise <[email protected]>
  • Re: [RFC] unify semaphore implementations
    • From: Paul Mackerras <[email protected]>
  • Re: [RFC] unify semaphore implementations
    • From: Benjamin LaHaise <[email protected]>

• Prev by Date: Re: [RFC] unify semaphore implementations
• Next by Date: Linux 2.6.11.8
• Previous by thread: Re: [RFC] unify semaphore implementations
• Next by thread: [PATCH] Tulip interrupt uses non IRQ safe spinlock
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]