linux-kernel - Re: [patch 17/18] tile: Use common threadinfo allocator

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: <4FA835FA.2090201@tilera.com>
Date:	Mon, 7 May 2012 16:52:10 -0400
From:	Chris Metcalf <cmetcalf@...era.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [patch 17/18] tile: Use common threadinfo allocator

On 5/7/2012 4:33 PM, Thomas Gleixner wrote:
> On Mon, 7 May 2012, Chris Metcalf wrote:
>
>> I think the only obvious
>> way is to override something in the threadinfo allocator.
> Wrong. The obvious way is to use the common code and add a special
> flag to it.

Well, that's overriding something in the threadinfo allocator :-)

In all seriousness, adding an arch-specific GFP flag sounds like it should
work OK for tile.  Thanks!

-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.com

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