From: Sebastien Decugis <sebastien.decugis@ext.bull.net>
To: linux-ia64@vger.kernel.org, linux-mm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: page fault scalability patch V12 [0/7]: Overview and performance tests
Date: Fri, 03 Dec 2004 15:49:51 +0100 [thread overview]
Message-ID: <1102085391.14792.102.camel@decugiss.frec.bull.fr> (raw)
[Gerrit Huizenga, 2004-12-02 16:24:04]
> Towards that end, there
> was a recent effort at Bull on the NPTL work which serves as a very
> interesting model:
> http://nptl.bullopensource.org/Tests/results/run-browse.php
> Basically, you can compare results from any test run with any other
> and get a summary of differences. That helps give a quick status
> check and helps you focus on the correct issues when tracking down
> defects.
Thanks Gerrit for mentioning this :)
Just an additional information -- the tool used to get this reporting
system is OSS and can be found here:
http://tslogparser.sourceforge.net
This tool is not mature yet, but it gives an overview of how useful a
test suite can be, when the results are easy to analyse...
It currently supports only the Open POSIX Test Suite, but I'd be happy
to work to enlarge the scope of this tool.
Regards,
Seb.
PS: please include me in reply as I'm not subscribed to the list...
-------------------------------
Sebastien DECUGIS
NPTL Test & Trace Project
http://nptl.bullopensource.org/
"You may fail if you try.
You -will- fail if you don't."
next reply other threads:[~2004-12-03 14:45 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 14:49 Sebastien Decugis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-22 15:00 page fault scalability patch V11 [1/7]: sloppy rss Hugh Dickins
2004-11-22 21:50 ` deferred rss update instead of " Christoph Lameter
2004-11-22 22:22 ` Linus Torvalds
2004-11-22 22:27 ` Christoph Lameter
2004-11-22 22:40 ` Linus Torvalds
2004-12-01 23:41 ` page fault scalability patch V12 [0/7]: Overview and performance tests Christoph Lameter
2004-12-02 0:10 ` Linus Torvalds
2004-12-02 0:55 ` Andrew Morton
2004-12-02 1:46 ` Christoph Lameter
2004-12-02 6:21 ` Jeff Garzik
2004-12-02 6:34 ` Andrew Morton
2004-12-02 6:48 ` Jeff Garzik
2004-12-02 7:02 ` Andrew Morton
2004-12-02 7:26 ` Martin J. Bligh
2004-12-02 7:31 ` Jeff Garzik
2004-12-02 18:10 ` cliff white
2004-12-02 18:17 ` Gerrit Huizenga
2004-12-02 20:25 ` linux-os
2004-12-02 18:43 ` cliff white
2004-12-06 19:33 ` Marcelo Tosatti
2004-12-02 16:24 ` Gerrit Huizenga
2004-12-02 17:34 ` cliff white
2004-12-02 19:48 ` Diego Calleja
2004-12-02 20:12 ` Jeff Garzik
2004-12-02 20:30 ` Diego Calleja
2004-12-02 21:08 ` Wichert Akkerman
2004-12-03 0:07 ` Francois Romieu
2004-12-02 7:00 ` Jeff Garzik
2004-12-02 7:05 ` Benjamin Herrenschmidt
2004-12-02 7:11 ` Jeff Garzik
2004-12-02 11:16 ` Benjamin Herrenschmidt
2004-12-02 14:30 ` Andy Warner
2005-01-06 23:40 ` Jeff Garzik
2004-12-02 18:27 ` Grant Grundler
2004-12-02 18:33 ` Andrew Morton
2004-12-02 18:36 ` Christoph Hellwig
2004-12-07 10:51 ` Pavel Machek
2004-12-09 8:00 ` Nick Piggin
2004-12-09 17:03 ` Christoph Lameter
2004-12-10 4:30 ` Nick Piggin
2004-12-09 18:37 ` Hugh Dickins
2004-12-10 4:26 ` Nick Piggin
2004-12-10 4:54 ` Nick Piggin
2004-12-10 5:06 ` Benjamin Herrenschmidt
2004-12-10 5:19 ` Nick Piggin
2004-12-10 12:30 ` Hugh Dickins
2004-12-10 18:43 ` Christoph Lameter
2004-12-10 21:43 ` Hugh Dickins
2004-12-10 22:12 ` Andrew Morton
2004-12-10 23:52 ` Hugh Dickins
2004-12-11 0:18 ` Andrew Morton
2004-12-11 0:44 ` Hugh Dickins
2004-12-11 0:57 ` Andrew Morton
2004-12-11 9:23 ` Hugh Dickins
2004-12-12 7:54 ` Nick Piggin
2004-12-12 9:33 ` Hugh Dickins
2004-12-12 9:48 ` Nick Piggin
2004-12-12 21:24 ` William Lee Irwin III
2004-12-17 3:31 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1102085391.14792.102.camel@decugiss.frec.bull.fr \
--to=sebastien.decugis@ext.bull.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).