public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Robert Love <rml@ximian.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: interrupt cpu time accounting?
Date: Sun, 29 Aug 2004 17:26:15 -0400	[thread overview]
Message-ID: <413249F7.50904@pobox.com> (raw)
In-Reply-To: <1093814102.2595.8.camel@localhost>

Robert Love wrote:
> On Sun, 2004-08-29 at 16:42 -0400, Jeff Garzik wrote:
> 
>>Does the kernel scheduler notice when a CPU spends a lot of time doing 
>>interrupt processing?
>>
>>For many network configurations you get the best cache affinity, etc. if 
>>you lock network interrupts to a single CPU.  However, on a box with 
>>high network load, that could mean that that CPU is spending more time 
>>processing interrupts than doing Real Work(tm).
>>
>>Will the scheduler "notice" this, and increasingly schedule processes 
>>away from the interrupt-heavy CPU?
> 
> 
> Nope, not explicitly anyhow.
> 
> Implicitly, at least, the load balancer will ensure that the runnable
> processes on the processor do not get "backed up" due to the delayed
> processing but you will still have the balanced minimum number of
> processes there.

What piece of code defines "balanced"?  :)


> I don't know whether the answer is to use cpu affinity and not schedule
> processes on that processor when you bind interrupts to it, or an
> automatic algorithm in the load balance for doing it, but that is a neat
> idea.

Less a neat idea, and more IMHO recognition of a problem that needs solving.

I am worried that processes will get starved if one CPU is _heavily_ 
loaded servicing interrupts, and the others are not.

Regards,

	Jeff



  reply	other threads:[~2004-08-29 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 20:42 interrupt cpu time accounting? Jeff Garzik
2004-08-29 21:15 ` Robert Love
2004-08-29 21:26   ` Jeff Garzik [this message]
2004-08-29 21:33     ` Robert Love

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=413249F7.50904@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rml@ximian.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox