On Tue, 2006-01-24 at 09:13 +0100, Ingo Molnar wrote:
> * Lee Revell <[email protected]> wrote:
>
> > On Tue, 2006-01-24 at 09:01 +0100, Ingo Molnar wrote:
> > > * Lee Revell <[email protected]> wrote:
> > >
> > > > On Tue, 2006-01-24 at 08:56 +0100, Ingo Molnar wrote:
> > > > > * Lee Revell <[email protected]> wrote:
> > > > >
> > > > > > I ported the latency tracer to 2.6.16 and got this 13ms latency within
> > > > > > a few hours. This is a regression from 2.6.15.
> > > > > >
> > > > > > It appears that RCU can invoke ipv4_dst_destroy thousands of times in
> > > > > > a single batch.
> > > > >
> > > > > could you try the PREEMPT_RCU patch below?
> > > >
> > > > Sure. If it works do you see this making it in 2.6.16? Otherwise we
> > > > still would have a regression...
> > >
> > > nope, that likely wont make v2.6.16, which is frozen already.
> > >
> >
> > How about just lowering maxbatch to 1000?
>
> does that fix the latency for you? I think "maxbatch=1000" should work
> as a boot parameter too.
>
Have not tested yet but it appears that will reduce it substantially:
$ grep "dst_destroy (dst_rcu_free)" /proc/latency_trace | wc -l
3027
This implies the latency would be reduced to ~4ms, still not great but
it will be overshadowed by rt_run_flush/rt_garbage_collect.
Lee
-
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]
