[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090803060944.GB20762@elte.hu>
Date: Mon, 3 Aug 2009 08:09:44 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "Frank Ch. Eigler" <fche@...hat.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Andi Kleen <andi@...stfloor.org>,
LKML <linux-kernel@...r.kernel.org>,
Jeff Mahoney <jeffm@...e.com>,
Chris Mason <chris.mason@...cle.com>,
Alexander Beregalov <a.beregalov@...il.com>,
Bron Gondwana <brong@...tmail.fm>,
Reiserfs <reiserfs-devel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Andrea Gelmini <andrea.gelmini@...il.com>,
"Trenton D. Adams" <trenton.d.adams@...il.com>,
Thomas Meyer <thomas@...3r.de>,
Alessio Igor Bogani <abogani@...ware.it>,
Marcel Hilzinger <mhilzinger@...uxnewmedia.de>,
Edward Shishkin <edward.shishkin@...il.com>
Subject: Re: [ANNOUNCE] Reiserfs/kill-bkl tree v2
* Frank Ch. Eigler <fche@...hat.com> wrote:
> Ingo Molnar <mingo@...e.hu> writes:
>
> >> 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.
>
> What guideline can you offer as to what is "due diligence" level
> of stress testing, as compared to delegating this task to
> eyeballed reviews + incidental use on the integration trees?
The kind of testing the VFS tree itself gets is a good starting
point i suspect - and it is a far more critical tree as it can
affects all filesystems. AFAICS the VFS tree relies on linux-next
and -mm for testing mostly and that's a good model IMO.
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/
Powered by blists - more mailing lists