Thread (9 messages) 9 messages, 6 authors, 2007-03-16

Re: [PATCH 2/9] Sched clock paravirt op fix.patch

From: Matt Mackall <hidden>
Date: 2007-03-16 21:43:50
Also in: lkml

On Tue, Mar 13, 2007 at 02:05:11PM -0700, Jeremy Fitzhardinge wrote:
Andi Kleen wrote:
quoted
It depends -- under heavy network load you can spend a long time
just processing interrupts.
Well, in that case you probably don't want to charge them to the process
which happens to be running at the time.
It's actually a good first-order approximation of the right thing to
do, as it will generally correlate with the userspace process
servicing that network load.

If not (for instance, with routing loads), then you'd basically expect
the charge to get spread around evenly in proportion to an
application's CPU usage.

The -rt kernel pushes most of the interrupt work off to threads, which
of course follow the same scheduling and accounting rules as
everything other thread.

-- 
Mathematics is the supreme nostalgia of our time.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help