Hide Forgot
Description of problem: Timer interrupt handling uses up to 20 usec Version-Release number of selected component (if applicable): 3.10.0-327.rt56.204.el7.x86_64 How reproducible: Steps to Reproduce: 1. run cpu bound process on isolcpu 2. trace for task switch 3. record time between task switches, where ksoftirqd is switched in/out Actual results: We see that cpu bound process is preempted for ksoftirqd, which does timer interrupt work, the switches back to cpu bound process. This work can take up to 20 usec Expected results: Timer interrupt work should not switch thread context and process timer interrupt work much faster (perhaps 2-3 usec, not sure of exact amount) Additional info: This is currently observed with a DPDK program running at fifo:95
What exactly is the bound task doing? ksoftirqd does timer work, and a timer interrupt can run. And things like task usage accounting can take 20 us.
Also, have you added nohz_full and rcu_nocb to that isolated CPU as well? That could help too.
We have no_full, but not rcu_nocb yet, so we will add that. I don't believe the user thread is doing anything other than some futex calls once in a while. We'll trace to see if anything else is going on with the user thread.
Andrew, were you able to do a trace to see if anything else was going on? Thanks, Beth
Karl, would it be possible to do another trace to see what is happening during the timer interrupt?
Andrew/Karl, any updates?
Andrew/Karl, any updates? If we can't get any additional updates, we will need to close this BZ.
We have not done a trace, and I am not sure when we will have opportunity to do so. We can close this and repoen when we have a trace.
Thank you, Andrew. As you suggest, we will close this issue. Please reopen the BZ if you do get a trace and we will take a look at it.