Re: Time loss after calling netif_rx() in a kernel thread

["Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>]

> Oh, you helped me this time again, like the last times...
> Mulyadi, you're the best - Many Thanks again! :-)

Oh no! :) Actually, I thought we learned from each other in this case.

Anyway, sched_yield() doesn't really work like it used to be in 2.4 or
old O(1) in 2.6. I just guess, maybe what you mean is schedule()?
yield()...IIRC...means putting current->need_resched to 1 or
TRUE....thus, it will be checked whenever scheduler is invoked.....and
that could be long sometimes.

BTW, -rt is real time...soft one..not hard real time. Just in case you
need bounded latency, whereas normal scheduler could give you
unpredictable or unbounded latency.

regards,

Mulyadi.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ