From: "Paul Larson" <plars@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel stress testing coverage
Date: Thu, 8 Mar 2001 14:57:35 -0600 [thread overview]
Message-ID: <OF50B88864.0721DA46-ON85256A09.006EE3FD@raleigh.ibm.com> (raw)
Alan Cox <alan@lxorguk.ukuu.org.uk> on 03/08/2001 02:06:06 PM
To: Paul Larson/Austin/IBM@ibmus
cc:
Subject: Re: Kernel stress testing coverage
>One thing I've been using for coverage (at least some coverage) is the
posix
>test suite
--------------------------
Are you talking about the same posix test suite that LSB is using? I've
looked into that a little, but here are the two problems I'm wanting to
address:
1. How much of the kernel is getting hit on a run of any given test? Even
an approximate percentage is fine as long as I can prove it.
2. I could run many many copies simultaneously I suppose and get some
stress, but I'd prefer to stress individual pieces one at a time. Those
pieces could then be mixed together in later runs for mixed load stress.
Additional mixed load tests will be performed with general applications
(web servers, databases, etc) for more of a "real world" environment, but I
want to have focused tests as well.
I'm betting that there are probably a LOT of quick and dirty test programs
that kernel hackers have written to expose a problem or thoroughly test a
piece of the kernel that they modified. These type of things would be
FYI this project will be going on sourceforge very soon. I want to have a
little more to start out with though and finish putting together a good
project description, testplans, etc. to post as soon as we put it on there.
I hate it when people start projects and you don't see any good information
about it for weeks.
Thanks,
Paul Larson
next reply other threads:[~2001-03-08 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 20:57 Paul Larson [this message]
2001-03-08 22:08 ` Alan Cox
2001-03-08 22:37 ` Roger Larsson
2001-03-15 12:17 ` Anton Blanchard
-- strict thread matches above, loose matches on Subject: below --
2001-03-08 19:52 Paul Larson
2001-03-08 21:28 ` Jeff Dike
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=OF50B88864.0721DA46-ON85256A09.006EE3FD@raleigh.ibm.com \
--to=plars@us.ibm.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®