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: Fri, 28 Mar 2008 10:32:34 +0100 [thread overview]
Message-ID: <20080328093234.GD30863@elte.hu> (raw)
In-Reply-To: <Pine.SGI.3.96.1080327115108.7873204e-100000@fergus.americas.sgi.com>
* Alan Mayer <ajm@sgi.com> wrote:
> > i think you got it right, yes. But ... this is just a quick
> > first-look suggestion from me, YMMV. Maybe you find a way to do it
> > much easier to just convert everything at once. I tend to do things
> > more gradually, in my experience it's very hard and time-consuming
> > to change the world all at once - it's hard both to you the
> > developer (you dont know whether it works until you have a very
> > substantial amount of code written - while in a more gradual
> > approach it can be converted one by one perhaps) - and it's hard for
> > users and fellow kernel hackers.
>
> I think I'll take a crack at it. Doing it in phases means I can
> invest a little less time and still give everyone a chance to see if
> they like it. And, the initial stuff seems like the area where people
> will be the most likely to have problems and/or suggestions. I have
> no idea how long it will take to get something out there. Stay tuned.
great! If your initial target for this is x86 (which has certainly the
most twisted IRQ architecture of all architectures) then we'd be glad to
host and test your patches in x86.git/latest - even if they touch
drivers and other core code. Once it's proven enough it could be
rehosted to -mm.
Ingo
prev parent reply other threads:[~2008-03-28 9:32 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
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 [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=20080328093234.GD30863@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