All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IRQ distribution in the 2.5.52  kernel
Date: Fri, 20 Dec 2002 03:15:18 -0800	[thread overview]
Message-ID: <20021220111518.GI25000@holomorphy.com> (raw)
In-Reply-To: <E88224AA79D2744187E7854CA8D9131DA5CE2F@fmsmsx407.fm.intel.com>

On Fri, Dec 20, 2002 at 01:08:18AM -0800, Kamble, Nitin A wrote:
> -static inline void balance_irq(int irq)
> +static inline void balance_irq (int cpu, int irq)
>  {
> -	irq_balance_t *entry = irq_balance + irq;
>  	unsigned long now = jiffies;
> -
> +	unsigned long allowed_mask;
> +	unsigned int new_cpu;
> +		
>  	if (clustered_apic_mode)
>  		return;

This can actually be done for clustered_apic_mode, just not as the
IO-APIC is currently programmed. It needs to either:

(1) develop awareness of multiple APIC buses and not attempt to perform
	physical mode interrupt delivery to non-existant destinations or
	overflow destination bitmasks to cpus not physically addressible
	from the local cluster

or

(2) the IO-APIC must be programmed for clustered hierarchical destinations
	in clustered setups, which probably isn't that hot an idea as the
	IO-APIC's in such setups usually have some affinity to the locally
	addressible physical destinations

These are both a PITA, but I thought I'd just sort of fling the issues
into open discussion since something touching this code hit the list.

There's some complexity in these schemes so unless you feel brave and/or
interested there's no need for you to run off and implement them etc.

No criticism of or flaws in your patch implied.


Thanks,
Bill

      reply	other threads:[~2002-12-20 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20  9:08 [PATCH] IRQ distribution in the 2.5.52 kernel Kamble, Nitin A
2002-12-20 11:15 ` William Lee Irwin III [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=20021220111518.GI25000@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitin.a.kamble@intel.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.