From: Mark Hounschell <markh@compro.net>
To: Stephane Charette <scharette@packeteer.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: performance impact of using noapic
Date: Wed, 03 Jul 2002 08:31:44 -0400 [thread overview]
Message-ID: <3D22EEB0.B3266763@compro.net> (raw)
In-Reply-To: 20020702192006Z316884-686+254@vger.kernel.org
Stephane Charette wrote:
>
> My questions are:
>
> 1) am I right in thinking that "noapic" will force all interrupts to be handled by 1 CPU?
Yes.
>
> 2) how would you force all interrupts from only 1 hardware device (and not all devices) to be handled by 1 processor, as hinted in the paragraph quoted above?
echo "00000001" > /proc/irq/19/smp_affinity
Will cause irq 19 to be serviced by processor 1
echo "00000003" > /proc/irq/19/smp_affinity
Will allow irq 19 to be serviced by processor 1 and 2
You could also do this in the driver if you wanted.
Note that this will not work when noapic is used..
Mark
prev parent reply other threads:[~2002-07-03 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 19:22 performance impact of using noapic Stephane Charette
2002-07-03 12:31 ` Mark Hounschell [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=3D22EEB0.B3266763@compro.net \
--to=markh@compro.net \
--cc=linux-kernel@vger.kernel.org \
--cc=scharette@packeteer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.