On Fri, 2005-12-30 at 20:29 -0800, Paul E. McKenney wrote:
> This should help in UP configurations, or in SMP configurations where
> all CPUs are doing call_rcu_bh() very frequently. I would not expect
> it to help in cases where one of several CPUs is frequently executing
> call_rcu_bh(), but where the other CPUs are either CPU-bound in user
> space or are in a tickful idle state.
This and net/decnet/dn_route.c are the only two uses of call_rcu_bh in
the kernel. And this one does not seem to be invoked frequently, it
took ~48 hours to show up in the latency tracer. Of course a server
workload might call it all the time.
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/
- References:
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
- Re: [patch] latency tracer, 2.6.15-rc7
[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]