All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Naresh <knaresh@india.hp.com>
Cc: Thibaut VARENE <varenet@esiee.fr>,
	"parisc-linux@lists.parisc-linux.org"
	<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Affined IRQs.
Date: Mon, 11 Aug 2003 09:44:49 -0600	[thread overview]
Message-ID: <20030811154449.GC20405@dsl2.external.hp.com> (raw)
In-Reply-To: <3F378CFE.2A12407@india.hp.com>

On Mon, Aug 11, 2003 at 06:03:03PM +0530, Naresh wrote:
> A couple of questions:
> 1. Do does this mean interrupts can go to any CPU?

Interrupts can be direct at any one CPU.
ia64 and parisc IPI use the same method as IO devices.

The code does a round-robin when assigning IO interrupts to CPUs.
ie assign interrupts to a sequential order of the CPUs.

A minor improvement would be to round-robin based on device class.
But I want this intelligence in user space, not the kernel.
NUMA machines want interrupts directed at CPUs in the same node
where the IO is "hosted".


> 2. If a CPU on an SMP system is stopped or its interrupts are blocked,
> will its interrupts automatically be serviced on another online CPU,

no. The interrupt must be "manually" redirected to another CPU.

> due to their non-affining nature?

Not sure what you mean here.

grant

> Regards,
> Naresh.
> 
> Thibaut VARENE wrote:
> 
> > > Hi,
> > > The IA-64 Linux kernel has a concept of affined IRQs, wherein IRQs can
> > > be bound/affined to particular CPUs. The affinity information shows up
> > > in '/proc/irq/#/smp_affinity'. I cannot see any affinity of IRQs to CPUs
> > > in PA ( iosapic.c and irq.c).. Is my understanding correct?
> > > Regards,
> > > Naresh.
> >
> > This has to be implemented for parisc and is on my todo list ;)
> >
> > (BTW, on vacation till Aug 25th.)
> >
> > Thibaut VARENE
> > The PA/Linux ESIEE Team
> > http://pateam.esiee.fr/
> > _______________________________________________
> > parisc-linux mailing list
> > parisc-linux@lists.parisc-linux.org
> > http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2003-08-11 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11  6:54 [parisc-linux] Affined IRQs Naresh
2003-08-11  7:43 ` Thibaut VARENE
2003-08-11 12:33   ` Naresh
2003-08-11 13:44     ` Thibaut VARÈNE
2003-08-11 16:00       ` Grant Grundler
2003-08-11 15:44     ` Grant Grundler [this message]
2003-08-11 15:49       ` Matthew Wilcox

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=20030811154449.GC20405@dsl2.external.hp.com \
    --to=grundler@parisc-linux.org \
    --cc=knaresh@india.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=varenet@esiee.fr \
    /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.