From: Michael Raymond <mraymond@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] ULI 2.6.12
Date: Fri, 01 Apr 2005 19:06:02 +0000 [thread overview]
Message-ID: <20050401130602.A123752@goliath.americas.sgi.com> (raw)
Here's a patch of the ULI code to Tony's pre-2.6.12 tree.
Signed-off-by: Michael A Raymond <mraymond@sgi.com>
I was able to show that ULIs cannot be scheduled onto other CPUs. For
every IRQ that a user requests it registers a standard handler. All IRQ
handlers are called out of do_IRQ(). It's not until do_IRQ() is called that
ia64_eoi() is called to complete the ACK and allow lower priority interrupts
into the system.
I've added a simple stats program that makes use of ULIs to the support
package on the web site (1). We've also found a case where their low
perturbation will be useful for user level profiling. I'll be writing that
up next.
Thanks,
Michael
(1) http://oss.sgi.com/projects/uli/
--
Michael A. Raymond Office: (651) 683-3434
Core OS Group Real-Time System Software
next reply other threads:[~2005-04-01 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 19:06 Michael Raymond [this message]
2005-04-04 0:22 ` [PATCH] ULI 2.6.12 Peter Chubb
2005-04-04 7:09 ` Christoph Hellwig
2005-04-04 13:31 ` Michael Raymond
2005-04-04 13:45 ` Christoph Hellwig
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=20050401130602.A123752@goliath.americas.sgi.com \
--to=mraymond@sgi.com \
--cc=linux-ia64@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