linux-kernel - Re: [PATCH] Allocate module.ref array dynamically

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]

Message-ID: <Pine.LNX.4.64.0811112113001.10592@quilx.com>
Date:	Tue, 11 Nov 2008 21:14:51 -0600 (CST)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
cc:	Eric Dumazet <dada1@...mosbay.com>, Takashi Iwai <tiwai@...e.de>,
	Andreas Gruenbacher <agruen@...e.de>,
	Jan Blunck <jblunck@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Mike Travis <travis@....com>
Subject: Re: [PATCH] Allocate module.ref array dynamically

On Wed, 12 Nov 2008, Rusty Russell wrote:

> On Wednesday 12 November 2008 08:36:26 Eric Dumazet wrote:
> > I believe Mike Travis has a better patch for this problem, partly using new
> > percpu allocator.
>
> Actually, I think this in in Christoph's hands now.  He's been wrangling with
> getting us a real per-cpu allocator.

Please use my new email address.... Otherwise I will not see this.

> There's something in linux-next, but I'm not sure of the status. Christoph, is
> this anticipated to make the next merge window, or am I best off merging a
> patch like Eric's for the moment?

Yes the patch in -next is for the next merge window. This should
actually have been in .28.

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