Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 8 Mar 2001 17:47:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 8 Mar 2001 17:47:41 -0500 Received: from mailg.telia.com ([194.22.194.26]:14609 "EHLO mailg.telia.com") by vger.kernel.org with ESMTP id ; Thu, 8 Mar 2001 17:47:30 -0500 Content-Type: text/plain; charset=US-ASCII From: Roger Larsson To: "Paul Larson" , linux-kernel@vger.kernel.org Subject: Re: Kernel stress testing coverage Date: Thu, 8 Mar 2001 23:37:55 +0100 X-Mailer: KMail [version 1.2] In-Reply-To: In-Reply-To: MIME-Version: 1.0 Message-Id: <01030823375501.03048@dox> Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, Here is a link to some memory usage related test programs: http://carpanta.dc.fi.udc.es/~quintela/memtest/ They have proven their value many times... /RogerL On Thursday 08 March 2001 21:57, Paul Larson wrote: > Alan Cox 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 > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Home page: none currently - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/