linux-kernel - [PATCH v2 1/3] [RFC] Generic Red-Black Trees

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: <4FC7FD23.6080800@att.net>
Date:	Thu, 31 May 2012 18:22:11 -0500
From:	Daniel Santos <danielfsantos@....net>
To:	linux-kernel@...r.kernel.org
CC:	Kent Overstreet <koverstreet@...gle.com>, tj@...nel.org,
	Peter Zijlstra <peterz@...radead.org>, axboe@...nel.dk,
	paul.gortmaker@...driver.com, Andi Kleen <andi@...stfloor.org>
Subject: [PATCH v2 1/3] [RFC] Generic Red-Black Trees

Well, I'm running on 3.4 patched with this generic rb tree
implementation in the fair scheduler (although these are slightly
cleaned up, so I still need to boot this version to make sure there's no
last minute snafus).  So I finally settled on a mechanism for the
type-safety, even though it's a big macro (not my first choice), it's
the mechanism that works on all versions of gcc that still matter.

This is still preliminary.  I have a user-space test program (that just
compiles the rbtree.h in userspace) and a test module that I want to
refine to do profiling & stress tests so that performance can be easily
checked on various architectures & compilers.  So here's the outstanding
list:

* insert_near not finished (low priority)
* find_near not yet tested
* augmented not yet tested

View attachment "0006-linux-bug.h-Add-BUILD_BUG_ON_NON_CONST-macros.patch" of type "text/x-patch" (3097 bytes)