lkml.org 
[lkml]   [2006]   [Jan]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: RCU latency regression in 2.6.16-rc1
From
Date
On Thu, 2006-01-26 at 11:18 -0800, Paul E. McKenney wrote:
> > Xorg-2154 0d.s. 213us : call_rcu_bh (rt_run_flush)
> > Xorg-2154 0d.s. 215us : local_bh_enable (rt_run_flush)
> > Xorg-2154 0d.s. 216us : local_bh_enable (rt_run_flush)
> > Xorg-2154 0d.s. 217us : local_bh_enable (rt_run_flush)
> > Xorg-2154 0d.s. 218us : local_bh_enable (rt_run_flush)
> > Xorg-2154 0d.s. 219us : local_bh_enable (rt_run_flush)
> > Xorg-2154 0d.s. 220us : local_bh_enable (rt_run_flush)
> > Xorg-2154 0d.s. 222us : local_bh_enable (rt_run_flush)
> > Xorg-2154 0d.s. 223us : call_rcu_bh (rt_run_flush)
> >
> > [ zillions of these deleted ]
> >
> > Xorg-2154 0d.s. 7335us : local_bh_enable (rt_run_flush)
>
> Dipankar's latest patch should hopefully address this problem.
>
> Could you please give it a spin when you get a chance?

Nope, no improvement at all, furthermore, the machine locked up once
under heavy disk activity.

I just got an 8ms+ latency from rt_run_flush that looks basically
identical to the above. It's still flushing routes in huge batches:

$ grep 'call_rcu_bh (rt_run_flush)' /proc/latency_trace | wc -l
2738

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-01-27 19:57    [W:0.098 / U:1.356 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site