rb_producer and rb_comsumer, kernel thread uses lot of CPU (~100%)
bandwidth every 10s.
bisection results commit:
[5092dbc96f3acdac5433b27c06860352dc6d23b9] ring-buffer: add benchmark and tester
I have read commit logs:
git log -r 5092dbc96f3acdac5433b27c06860352dc6d23b9
Is it correct behavior for these thread to consume this much cpu
bandwidth even if someone selects rb benchmarks config options?
thanks
-tej
On Fri, 2009-07-03 at 11:36 +0530, Tej wrote:
> rb_producer and rb_comsumer, kernel thread uses lot of CPU (~100%)
> bandwidth every 10s.
>
> bisection results commit:
> [5092dbc96f3acdac5433b27c06860352dc6d23b9] ring-buffer: add benchmark and tester
> I have read commit logs:
> git log -r 5092dbc96f3acdac5433b27c06860352dc6d23b9
>
> Is it correct behavior for these thread to consume this much cpu
> bandwidth even if someone selects rb benchmarks config options?
Yes, that's a benchmark module, not something to be running on a
production system. It consumes a lot of CPU time, because it is running
a constant benchmark, and tests.
-- Steve