Ingo Molnar <[email protected]> wrote: > so how about the following, different approach: anyone who has a tasklet > in any performance-sensitive codepath, please yell now. The Siemens Gigaset ISDN base driver uses tasklets in its isochronous data paths. These will be scheduled for each completion of an isochronous URB, or every 8 msec for each of the four isochronous pipes if both B channels are connected. The driver uses three URBs for each pipe, always maintaining two in flight while processing the third one. So the tasklet has to run within 16 ms from being scheduled in order to avoid packet loss (in the receive path) or data underrun (in the transmit path). Does that qualify as performance sensitive for the purpose of this discussion? Thanks, Tilman -- Tilman Schmidt E-Mail: [email protected] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: [RFC PATCH 0/6] Convert all tasklets to workqueues
- From: Stephen Hemminger <[email protected]>
- Re: [RFC PATCH 0/6] Convert all tasklets to workqueues
- From: Steven Rostedt <[email protected]>
- Re: [RFC PATCH 0/6] Convert all tasklets to workqueues
- References:
- Re: [RFC PATCH 0/6] Convert all tasklets to workqueues
- From: [email protected] (Jonathan Corbet)
- Re: [RFC PATCH 0/6] Convert all tasklets to workqueues
- Prev by Date: Re: Oops in a driver while using SLUB as a SLAB allocator
- Next by Date: Re: i386 boot fail, EIP in __change_page_attr:166
- Previous by thread: Re: [RFC PATCH 0/6] Convert all tasklets to workqueues
- Next by thread: Re: [RFC PATCH 0/6] Convert all tasklets to workqueues
- Index(es):
 |