linux-kernel - [PATCH 0/4] RT: RT-Overload/Sched v3

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: <20071016160226.5202.53965.stgit@novell1.haskins.net>
Date:	Tue, 16 Oct 2007 12:08:52 -0400
From:	Gregory Haskins <ghaskins@...ell.com>
To:	Steven Rostedt <rostedt@...dmis.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	RT <linux-rt-users@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Gregory Haskins <ghaskins@...ell.com>
Subject: [PATCH 0/4] RT: RT-Overload/Sched v3

v3 contains the following changes since v2:

This is still based on 23-rt1 + Steve's last public patch (I think Steve has a
newer version available, but we have not rebased yet).

1) No longer includes the per-cpu-rtoverload patch, since Steve has already
   ACKed it
2) Dropped the affinity patch because it was buggy.  Will revisit later
3) Dropped the pull-patch, since it was RFC only anyway.  Will revisit later
4) Addressed review comments/feedback (added patch descriptions across the
   board, moved semi-colon in while loop, removed superfluous
   smp_processor_id() etc.
5) Got rid of the second TASK_PREEMPTS_CURR() check, since my anaylsys
   determined it was not needed.

With this patch series applied, my RT test now passes and we get an average of
23us wake-up latency under load. You can find the test here: 

 ftp://ftp.novell.com/dev/ghaskins/preempt.cc

Note: Do not use the "affinity" option, as the validator has a bug related to
it and may yield a false negative.

Regards,
-Greg

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