public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
To: listmonkey@neo.relay-host.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP CPU affinity questions
Date: Wed, 02 Nov 2005 09:39:27 -0700	[thread overview]
Message-ID: <4368EBBF.2000302@wolfmountaingroup.com> (raw)
In-Reply-To: <20051102175022.13637.qmail@neo.relay-host.net>

listmonkey@neo.relay-host.net wrote:

>Hi-
>
>I am trying to use a quad Opteron motherboard with SMP Kernel 2.6.5 for a quasi-real-time task.
>I need to assign all processes to specific CPUs, including interrupt handlers.
>I have had success using sched_setaffinity() to set the CPU for processes I create, but I am unable,
>as root, to force system processes to move to another CPU.  Any ideas?
>
>I can find no documentation about how to force an interrupt handler to a specific CPU - is this
>possible without modifying the kernel?
>
>  
>


IOApic's support binding of interrupt delivery in intel based platforms, 
but I am unaware of tools which force this
setting by default on Linux, but someone else may be able to point you 
in that direction.  Most folks code APIC ICC delivery to
AV_LOPRI (meaning lowest priority processor gets next interrupt).   This 
is advantageous for cache coherency since the IRQ code
is probaby still in that processors cache.  You may have to modify the 
kernel.  Linux doesn't allow processors to be shutdown and
reactiviated real time, it just starts them and lets them run, so you 
don;t have to worry about the case of migrating interrupts
off pinned APICs.  The APIC supports what you are asking for, but I am 
not certain anyone implemented anything other
than AV_LOPRI settings by default in the IO APIC code.  I would suggest 
you look over the IO APIC Code -- this is a lot
of work, BTW.

Jeff

>--Pete
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>


  reply	other threads:[~2005-11-02 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 17:50 SMP CPU affinity questions listmonkey
2005-11-02 16:39 ` Jeffrey V. Merkey [this message]
2005-11-05 23:48   ` Zwane Mwaikambo
2005-11-06  7:56   ` Arjan van de Ven
2005-11-02 18:54 ` Lee Revell

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=4368EBBF.2000302@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=listmonkey@neo.relay-host.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