From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Chinner <dgc@sgi.com>, Eric Sandeen <sandeen@sandeen.net>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: qa 166 failure on f8 kernel
Date: Wed, 8 Aug 2007 23:17:13 +1000 [thread overview]
Message-ID: <20070808131713.GR52011508@sgi.com> (raw)
In-Reply-To: <20070808131319.GA11451@infradead.org>
On Wed, Aug 08, 2007 at 02:13:19PM +0100, Christoph Hellwig wrote:
> On Wed, Aug 08, 2007 at 02:08:04PM +1000, David Chinner wrote:
> > On Tue, Aug 07, 2007 at 09:58:50PM -0500, Eric Sandeen wrote:
> > > yeah, figured it had something to do w/ the ia64 weenies when I saw the
> > > 32 vs. 8, factor of 4 ... fine, fine, my bad. :)
> >
> > No, not your bad. Mine if anyones because I wrote the test.
>
> Ia64 supports 4k, 8k, 16k and 64k base pagesize. Time to add a little
> script to make the pagesize random for your kernel builds?
Interesting idea. Definitely worth considering for the randomised
mkfs/mount option config QA runs we already do....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-08-08 13:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 1:39 qa 166 failure on f8 kernel Eric Sandeen
2007-08-08 2:56 ` David Chinner
2007-08-08 2:58 ` Eric Sandeen
2007-08-08 4:08 ` David Chinner
2007-08-08 4:11 ` Eric Sandeen
2007-08-08 4:16 ` Eric Sandeen
2007-08-08 4:19 ` David Chinner
2007-08-08 4:28 ` Eric Sandeen
2007-08-08 4:57 ` Barry Naujok
2007-08-08 5:00 ` Eric Sandeen
2007-08-08 13:13 ` Christoph Hellwig
2007-08-08 13:17 ` David Chinner [this message]
2007-08-08 4:13 ` Alex Elder
[not found] ` <D59801BCA402F5418C040937230AF7E00B9A8E@mtv-amer002e--3.americas.sgi.c om>
2007-08-08 5:47 ` nscott
2007-08-08 4:19 ` Barry Naujok
2007-08-08 4:18 ` Eric Sandeen
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=20070808131713.GR52011508@sgi.com \
--to=dgc@sgi.com \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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