mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@sgi.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] x86/apic: limit irq affinity
Date: Thu, 15 Oct 2009 08:50:39 -0500	[thread overview]
Message-ID: <20091015135039.GA24455@sgi.com> (raw)
In-Reply-To: <4AD6B364.2050801@kernel.org>

On Wed, Oct 14, 2009 at 10:30:12PM -0700, Yinghai Lu wrote:
> Dimitri Sivanich wrote:
> > This patch allows for hard restrictions to irq affinity via a new cpumask and
> > device node value in the irq_cfg structure.
> > 
> > The mask forces IRQ affinity to remain within the specified cpu domain.
> > On some UV systems, this domain will be limited to the nodes accessible
> > to the given node.  Currently other X86 systems will have all bits in
> > the cpumask set, so non-UV systems will remain unaffected at this time.
> > 
> 
> can you check if we can reuse target_cpus for this purpose?
>
 
Yinghai,

The 'target_cpus' mask is in struct 'apic'.  It is a platform level mask
(only one mask per platform).

The 'allowed' mask that I am adding is a per irq level mask (one mask per irq).
Each irq might be coming from a device attached to a different node, and each
of those nodes might require its irqs to have a different mask.

For example, say there is a pci device attached to node 2.  Node 2 might only
want (or be able) to route its interrupts to nodes 0-127.  It would have
'allowed' mask allowing only processors existing on the first 128 nodes.  A
pci device attached to node 150 would have a different allowed mask, since it
would route its interrupts to a different set of nodes.

Use of something like 'target_cpus' would require recalculating this every
time someone changes affinity, instead of just 'and'ing in the mask.

Dimitri

  reply	other threads:[~2009-10-15 14:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 16:02 [PATCH] x86: SGU UV Fix irq affinity for hub based interrupts Dimitri Sivanich
2009-09-30 16:10 ` Robin Holt
2009-10-12 19:34 ` Ingo Molnar
2009-10-13 20:32   ` [PATCH] x86: Move SGI UV functionality out of generic IO-APIC code Dimitri Sivanich
2009-10-14  8:18     ` [tip:x86/apic] x86, apic: " tip-bot for Dimitri Sivanich
     [not found]   ` <20091012193704.GA8708@sgi.com>
     [not found]     ` <20091014071014.GK784@elte.hu>
     [not found]       ` <20091014120225.GA9674@sgi.com>
     [not found]         ` <20091014122653.GA15048@elte.hu>
2009-10-15  1:13           ` [PATCH v2] x86/apic: limit irq affinity Dimitri Sivanich
2009-10-15  5:30             ` Yinghai Lu
2009-10-15 13:50               ` Dimitri Sivanich [this message]
2009-10-20 12:56                 ` Dimitri Sivanich
2009-10-20 13:38                   ` [PATCH v3] " Dimitri Sivanich
2009-10-20 18:58                     ` Yinghai Lu
2009-10-21  1:06                       ` Dimitri Sivanich
2009-10-21  1:12                     ` [PATCH v4] " Dimitri Sivanich
2009-11-08 13:07                       ` [tip:x86/apic] x86/apic: Limit " tip-bot for Dimitri Sivanich
2009-11-08 14:53                         ` Ingo Molnar
2009-11-09 16:02                           ` Dimitri Sivanich
2009-11-10  4:40                             ` Ingo Molnar
2009-11-10 16:31                               ` Dimitri Sivanich
2009-11-10 17:19                                 ` Ingo Molnar
2009-11-10 18:57                                   ` [PATCH] Remove SMP ifdef from irq_desc Dimitri Sivanich
2009-11-16 10:49                                     ` Thomas Gleixner
2009-10-14  8:17 ` [tip:x86/apic] x86: SGI UV: Fix irq affinity for hub based interrupts tip-bot for Dimitri Sivanich

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=20091015135039.GA24455@sgi.com \
    --to=sivanich@sgi.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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

Powered by JetHome