* ring-buffer: Kernel threads cpu utilization.
@ 2009-07-03 6:06 Tej
2009-07-03 13:06 ` Steven Rostedt
0 siblings, 1 reply; 2+ messages in thread
From: Tej @ 2009-07-03 6:06 UTC (permalink / raw)
To: linux-kernel; +Cc: srostedt
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ring-buffer: Kernel threads cpu utilization.
2009-07-03 6:06 ring-buffer: Kernel threads cpu utilization Tej
@ 2009-07-03 13:06 ` Steven Rostedt
0 siblings, 0 replies; 2+ messages in thread
From: Steven Rostedt @ 2009-07-03 13:06 UTC (permalink / raw)
To: Tej; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-07-03 13:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-07-03 6:06 ring-buffer: Kernel threads cpu utilization Tej
2009-07-03 13:06 ` Steven Rostedt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome