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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 20 Oct 2009 15:14:08 +0900 From: Tejun Heo <tj@...nel.org> To: Jiri Kosina <jkosina@...e.cz> CC: Jeff Mahoney <jeffm@...e.com>, Peter Zijlstra <peterz@...radead.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Tony Luck <tony.luck@...el.com>, Fenghua Yu <fenghua.yu@...el.com>, linux-ia64@...r.kernel.org Subject: Re: Commit 34d76c41 causes linker errors on ia64 with NR_CPUS=4096 Tejun Heo wrote: > Jiri Kosina wrote: >> So how about something along the lines below? (completely untested as >> well) >> >> From: Jiri Kosina <jkosina@...e.cz> >> Subject: sched: move rq_weight data array out of .percpu >> >> Commit 34d76c41 introduced percpu array update_shares_data, size of which >> being proportional to NR_CPUS. Unfortunately this blows up ia64 for large >> NR_CPUS configuration, as ia64 allows only 64k for .percpu section. >> >> Fix this by allocating this array dynamically and keep only pointer to it >> percpu. > > Looks good to me from percpu POV. Oh... one thing. If you're doing dynamic allocation you can use nr_cpu_ids instead of NR_CPUS. -- tejun -- 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