linux-kernel - [PATCH 0/3] kref: inline and barriers

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: <20111210104341.592561407@chello.nl>
Date:	Sat, 10 Dec 2011 11:43:41 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	gregkh@...e.de, akpm@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, ostrikov@...dia.com,
	adobriyan@...il.com, eric.dumazet@...il.com, mingo@...e.hu
Subject: [PATCH 0/3] kref: inline and barriers

>>From time to time people on #kernelnewbies ask what the difference is between
kref and using atomic_t yourself. And I keep having to tell them that kref is
the slow and weird option.

These patches try and cure some of that, it inlines all functions and removes
the superfluous memory barriers that are there for no good reason at all.

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