From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Randy <randys@evcom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dedicated Interrupt handling on SMP
Date: Fri, 25 May 2001 22:38:41 +0200 [thread overview]
Message-ID: <20010525223841.V754@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <3B0E8B9F.CFBEAC59@evcom.net>
In-Reply-To: <3B0E8B9F.CFBEAC59@evcom.net>; from randys@evcom.net on Fri, May 25, 2001 at 12:43:11PM -0400
On Fri, May 25, 2001 at 12:43:11PM -0400, Randy wrote:
> I'm trying to find the easiest way to to deidcate one CPU to responding
> to a specific Interrupt request.
> That CPU should only listen for that request while all other CPU should
> ignore the interrupt.
cat /proc/irq/*/smp_affinity
There you can select on which if the 32 CPUs Linux should handle
this IRQ.
Read Documentation/IRQ-affinity.txt for more.
Regards
Ingo Oeser
--
To the systems programmer,
users and applications serve only to provide a test load.
prev parent reply other threads:[~2001-05-25 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 16:43 Randy
2001-05-25 20:38 ` Ingo Oeser [this message]
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=20010525223841.V754@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randys@evcom.net \
/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®