linux-kernel - Re: [PATCH] x86_64: resize NR_IRQS for large machines (re-submit)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 28 Mar 2008 10:32:34 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Alan Mayer <ajm@....com>
Cc:	torvalds@...ux-foundation.org,
	linux-kernel list <linux-kernel@...r.kernel.org>,
	Robin Holt <holt@....com>, Jack Steiner <steiner@....com>,
	Russ Anderson <rja@....com>
Subject: Re: [PATCH] x86_64: resize NR_IRQS for large machines (re-submit)


* Alan Mayer <ajm@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/