Ingo Molnar wrote:
so how about the following, different approach: anyone who has a tasklet
in any performance-sensitive codepath, please yell now. We'll also do a
proactive search for such places. We can convert those places to
softirqs, or move them back into hardirq context. Once this is done -
and i doubt it will go beyond 1-2 places - we can just mass-convert the
other 110 places to the lame but compatible solution of doing them in a
global thread context.
Color me unconvinced.
Tasklets fill a niche not filled by either workqueues (slower, requiring
context switches, and possibly much latency is all wq's processes are
active) or softirqs (limited number of them, not flexible at all).
Sure, tasklets kick over to ksoftirqd, but not immediately, and therein
lies their value.
And moving code -back- into hardirq is just the wrong thing to do, usually.
This proposal is ENTIRELY derived from "not convenient to my project"
logic AFAICS, rather than the more sound "not needed in the kernel."
Jeff
-
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/
[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]
