public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alan Mayer <ajm@sgi.com>
Cc: torvalds@linux-foundation.org,
	linux-kernel list <linux-kernel@vger.kernel.org>,
	Robin Holt <holt@sgi.com>, Jack Steiner <steiner@sgi.com>,
	Russ Anderson <rja@sgi.com>
Subject: Re: [PATCH] x86_64: resize NR_IRQS for large machines (re-submit)
Date: Wed, 26 Mar 2008 23:24:51 +0100	[thread overview]
Message-ID: <20080326222450.GA11621@elte.hu> (raw)
In-Reply-To: <Pine.SGI.3.96.1080326163708.7873204c-100000@fergus.americas.sgi.com>


* Alan Mayer <ajm@sgi.com> wrote:

> > but it doesnt really depart from the current status quo of huge 
> > [NR_IRQS] arrays either. Patches that make NR_IRQS a variable are 
> > welcome :)
> 
> Good luck with that.  If i come up with something that's elegant 
> enough to make it worth the risk, I'll let you know.  Changing NR_IRQS 
> to a variable touches every arch and a lot of drivers.  Someone is 
> bound to choke on it, so it has to be something worth fighting for.

well, i dont it has to be (or it should be) an all or nothing patch, 
given the complexity and risks involved.

- we should first introduce a nr_irqs variable and a Kconfig switch 
  (say CONFIG_ARCH_HAS_DYNAMIC_NR_IRQS) for architectures to toggle. If 
  the switch is toggled, nr_irqs is a variable, otherwise it's a carbon 
  copy of NR_IRQS. Some array-definition, declaration and initialization 
  wrappers are provided as well.

- then the core code, x86 and most drivers can be converted to nr_irqs.
  The switch might initially even be user-selectable if
  CONFIG_DEBUG_KERNEL, to ease regression testing.

- other architectures will follow one by one, fixing their
  arch-dependent drivers as well in the process

- finally we get rid of the wrappers.

	Ingo

  reply	other threads:[~2008-03-26 22:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 21:11 [PATCH] x86_64: resize NR_IRQS for large machines (re-submit) Alan Mayer
2008-03-26 21:23 ` Ingo Molnar
2008-03-26 21:40   ` Alan Mayer
2008-03-26 22:24     ` Ingo Molnar [this message]
2008-03-27 16:16       ` Alan Mayer
2008-03-27 16:33         ` Ingo Molnar
2008-03-27 16:53           ` Alan Mayer
2008-03-28  9:32             ` Ingo Molnar

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=20080326222450.GA11621@elte.hu \
    --to=mingo@elte.hu \
    --cc=ajm@sgi.com \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rja@sgi.com \
    --cc=steiner@sgi.com \
    --cc=torvalds@linux-foundation.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