linux-kernel - Re: Ten percent test

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: <20070409180356.GA17739@elte.hu>
Date:	Mon, 9 Apr 2007 20:03:56 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	William Lee Irwin III <wli@...omorphy.com>
Cc:	Mike Galbraith <efault@....de>,
	Gene Heskett <gene.heskett@...il.com>,
	linux-kernel@...r.kernel.org, Con Kolivas <kernel@...ivas.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Ten percent test

* William Lee Irwin III <wli@...omorphy.com> wrote:

> I strongly suggest assembling a battery of cleanly and properly 
> written, configurable testcases, and scripting a series of regression 
> tests as opposed to just randomly running kernel compiles and relying 
> on Braille.

there's interbench, written by Con (with the purpose of improving 
RSDL/SD), which does exactly that, but vanilla and SD performs quite the 
same in those tests.

it's quite hard to test interactivity, because it's both subjective and 
because even for objective workloads, things depend so much on exact 
circumstances. So the best way is to wait for actual complaints, and/or 
actual testcases that trigger badness, and victims^H^H^H^H^H testers.

(also note that often it needs _that precise_ workload to trigger some 
badness. For example make -j depends on the kind of X shell terminal 
that is used - gterm behaves differently from xterm, etc.)

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