From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jamesclv@us.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Summit interrupt routing patches
Date: Fri, 18 Jan 2002 23:15:41 +0000 (GMT) [thread overview]
Message-ID: <E16RiEX-0008Bi-00@the-village.bc.nu> (raw)
In-Reply-To: <200201182246.g0IMkbq10990@butler1.beaverton.ibm.com> from "James Cleverdon" at Jan 18, 2002 02:46:36 PM
> alternative is much more invasive: adding interrupt code to adjust XTPRs,
> hacks to the scheduler to somehow encapsulate task priority in 4 bits, etc.
Is it necessary to try something complex. We already keep per cpu/per irq
data and if you have a lot of interrupts it feels like you can handwave them
to be roughly the same amount of cpu load.
Given that is it enough to once a second shuffle the irqs around to try and
get a rough balance based on a simple decaying history. Then all it needs
is a regular timer event to do what the hardware hasnt
next prev parent reply other threads:[~2002-01-18 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 22:46 James Cleverdon
2002-01-18 23:15 ` Alan Cox [this message]
2002-01-19 0:18 ` James Cleverdon
2002-01-19 1:11 ` David S. Miller
2002-01-22 0:59 ` James Cleverdon
2002-01-19 1:18 ` Alan Cox
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=E16RiEX-0008Bi-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jamesclv@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®