Re: "upping" a semaphore from interrupt context?

Am Samstag, 23. Juni 2007 schrieb Satyam Sharma:
>          * 3. set up a timer and schedule another function to service the
>          *    interrupt / do what needs to be done then, hopefully the mutex
>          *    would be uncontended then => *gargh*

You could use schedule_work(). However then why not use it always.
This would make sense if what you want to do is outright trivial.

	Regards
		Oliver
-
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/

---

• Follow-Ups:
  • Re: "upping" a semaphore from interrupt context?
    • From: "Satyam Sharma" <[email protected]>

• References:
  • "upping" a semaphore from interrupt context?
    • From: [email protected] (Florin Iucha)
  • Re: "upping" a semaphore from interrupt context?
    • From: Arnd Bergmann <[email protected]>
  • Re: "upping" a semaphore from interrupt context?
    • From: "Satyam Sharma" <[email protected]>

• Prev by Date: Re: "upping" a semaphore from interrupt context?
• Next by Date: Re: How innovative is Linux?
• Previous by thread: Re: "upping" a semaphore from interrupt context?
• Next by thread: Re: "upping" a semaphore from interrupt context?
• 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]