linux-kernel - [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86

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

Message-Id: <20071130064305.459255715@sgi.com>
Date:	Thu, 29 Nov 2007 22:43:05 -0800
From:	Christoph Lameter <clameter@....com>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Thomas Gleixner <tglx@...utronix.de>
Subject: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64

This patchset allows the use of x86_32 percpu ops on x86_64 while maintaining
%gs pointing to the pda. It does that by moving the x86_64 pda into
the percpu area (thereby pointing %gs at the per cpu area) and then
relocating the x86_64 per cpu variables to start at 0.

Patch applies on top of the per cpu cleanup patches V2.
See http://marc.info/?l=linux-kernel&m=119628478316525&w=2

Ultimately I think we can make the per cpu accessors arch independent
(see the RFC at http://marc.info/?l=linux-kernel&m=119552126330405&w=2).
There is a performance benefit from using these in core code.

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