From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752524AbZHBOVg (ORCPT ); Sun, 2 Aug 2009 10:21:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752001AbZHBOVg (ORCPT ); Sun, 2 Aug 2009 10:21:36 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:42655 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751717AbZHBOVf (ORCPT ); Sun, 2 Aug 2009 10:21:35 -0400 Date: Sun, 2 Aug 2009 16:21:00 +0200 From: Ingo Molnar To: Frederic Weisbecker Cc: Andi Kleen , LKML , Jeff Mahoney , Chris Mason , Alexander Beregalov , Bron Gondwana , Reiserfs , Al Viro , Andrea Gelmini , "Trenton D. Adams" , Thomas Meyer , Alessio Igor Bogani , Marcel Hilzinger , Edward Shishkin Subject: Re: [ANNOUNCE] Reiserfs/kill-bkl tree v2 Message-ID: <20090802142100.GA21160@elte.hu> References: <20090731174642.GA6539@nowhere> <20090801081141.GA18036@basil.fritz.box> <20090801155335.GA4836@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090801155335.GA4836@nowhere> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Frederic Weisbecker wrote: > > e.g. running all the file system stress tests from LTP would be > > a good idea, ideally multiple at a time on a multi processor > > system on a ram disk or perhaps AIM9. > > Yeah good idea. But again, I fear my laptop hasn't enough memory > to support big enough ramdisks mount points to host selftests. Well, dont waste too much time on it (beyond the due diligence level) - Andi forgot that the right way to stress-test patches is to get through the review process and then through the integration trees which have far more test exposure than any single contributor can test. Patch submitters cannot possibly test every crazy possibility that is out there - nor should they: it just doesnt scale. What we expect people to do is to write clean patches, to test the bits on their own boxes and submit them to lkml and address specific review feedback. Ingo