linux-kernel - Re: [Bug #14467] Linker errors on ia64 with NR

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 29 Oct 2009 14:39:19 -0400 (EDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Jiri Kosina <jkosina@...e.cz>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>, Jeff Mahoney <jeffm@...e.com>,
	"Luck, Tony" <tony.luck@...el.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Peter Zijlstra <peterz@...radead.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [Bug #14467] Linker errors on ia64 with NR_CPUS=4096

On Tue, 27 Oct 2009, Jiri Kosina wrote:

> On Tue, 27 Oct 2009, Christoph Lameter wrote:
>
> > The NR_CPUS array in the percpu section needs to be removed.
> >
> > A simple fix would be to allocate the rq_weight per cpu array
> > dynamically.
>
> There already are two patches for this acked by Ingo/Tejun, which Tejun is
> going to take through his tree tomorrow.
>
> 	http://lkml.org/lkml/2009/10/27/132

per cpu alloc from an atomic context without passing gfp flags through to
the page allocator? That does not look right. Sure wish that the percpu
allocator would be working from atomic contexts for other cases.

> 	http://lkml.org/lkml/2009/10/27/215

There is still heavy percpu use because of the patch for machines with
large numbers of processors. Another solution would be better that does
not require a N^2 sized array.

--
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/