From: nscott@aconex.com
To: Alex Elder <aelder@sgi.com>
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 15:47:29 +1000 (EST) [thread overview]
Message-ID: <37268.192.168.3.1.1186552049.squirrel@mail.aconex.com> (raw)
In-Reply-To: <D59801BCA402F5418C040937230AF7E00B9A8E@mtv-amer002e--3.americas.sgi.c om>
>> From: xfs-bounce@oss.sgi.com
>> [mailto:xfs-bounce@oss.sgi.com]On Behalf Of
>> David Chinner
>> Sent: Tuesday, August 07, 2007 9:56 PM
>> To: Eric Sandeen
>> Cc: xfs-oss
>> Subject: Re: qa 166 failure on f8 kernel
> ...
>> mmap dirties entire pages. page size differs between platforms -
>> ia64 = 16k, x86 = 4k - so the size of the extent allocated is
>> different. Guess what platform I wrote the test on and use as my
>> primary platform?
>>
>> The output needs better filtering, methinks.
>
> Could the test be changed so the output is pagesize independent
> rather than filtering the output? Or maybe the test should
> use a buffer size that's the LCM of all supported page sizes.
>
FWIW, xfs-cmds/xfstests/src/feature.c will tell you the page size (-s);
with that you can accurately filter the output and not lose any info.
cheers.
--
Nathan
next prev parent reply other threads:[~2007-08-08 5:47 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
2007-08-08 4:13 ` Alex Elder
[not found] ` <D59801BCA402F5418C040937230AF7E00B9A8E@mtv-amer002e--3.americas.sgi.c om>
2007-08-08 5:47 ` nscott [this message]
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=37268.192.168.3.1.1186552049.squirrel@mail.aconex.com \
--to=nscott@aconex.com \
--cc=aelder@sgi.com \
--cc=dgc@sgi.com \
--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