Herbert Xu a écrit :
On Fri, May 25, 2007 at 08:50:20AM +0200, Eric Dumazet wrote:
If this patch really helps, this means cond_resched_softirq()
doesnt work at all and should be fixed, or just zapped as it
is seldom used.
cond_resched_softirq lets other threads run if they want to.
It doesn't run pending softirq's at all. In fact, it doesn't
even wake up ksoftirqd.
I am very glad you fixed /proc/net/tcp, but I would like to
understand why this cond_resched_softirq() even exist.
Its name and behavior dont match at all.
The only remaining use is in __release_sock().
Should we schedule threads, or ksoftirqd as well in this function ?
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
