public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Subject: interrupt cpu time accounting?
Date: Sun, 29 Aug 2004 16:42:16 -0400	[thread overview]
Message-ID: <41323FA8.80203@pobox.com> (raw)


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?

	Jeff




             reply	other threads:[~2004-08-29 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 20:42 Jeff Garzik [this message]
2004-08-29 21:15 ` interrupt cpu time accounting? Robert Love
2004-08-29 21:26   ` Jeff Garzik
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=41323FA8.80203@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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