| 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
| ||
|
Message-Id: <20081113.162144.155677034.davem@davemloft.net> Date: Thu, 13 Nov 2008 16:21:44 -0800 (PST) From: David Miller <davem@...emloft.net> To: travis@....com Cc: paulus@...ba.org, akpm@...ux-foundation.org, yinghai@...nel.org, mingo@...e.hu, tglx@...utronix.de, hpa@...or.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH] sparse_irq aka dyn_irq v13 From: Mike Travis <travis@....com> Date: Thu, 13 Nov 2008 16:15:12 -0800 > David Miller wrote: > > From: Mike Travis <travis@....com> > > Date: Thu, 13 Nov 2008 15:11:29 -0800 > > > > We use a value of 256 and I've been booting linux on 128 cpu sparc64 > > systems with lots of PCI-E host controllers (and others have booted it > > on even larger ones). All of which have several NUMA domains. > > > > It's not an issue. > > Are you saying that having a fixed count of IRQ's is not an issue? With > NR_CPUS=4096 what would you fix it to? (Currently it's NR_CPUS * 32 > but that might not be sufficient.) Would NR_CPUS=16384 make it an issue? Nope, and nope. I frequently run kernels with NR_CPUS set to huge values. It seems that the issue of x86 is that it has it's IRQ count tied to the number of cpus, that's not very intelligent. Perhaps that part should be rearranged somehow? -- 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/
Powered by blists - more mailing lists