From: Gurudas Pai <gurudas.pai@oracle.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: fio@vger.kernel.org
Subject: Re: request for job files
Date: Fri, 24 Apr 2009 10:30:33 +0530 [thread overview]
Message-ID: <49F14771.6040004@oracle.com> (raw)
In-Reply-To: <20090422132257.GR4593@kernel.dk>
> The sample job files shipped with fio are (generally) pretty weak, and
> I'd really love for the selection to be better.
Hi,
Please see if following jobfile is useful. This was used to uncover 2
kernel bugs with mainline kernel.
# this jobfile was used to uncover 2 mainline kernel bugs.
#OOPS IN BIO_GET_NR_VECS+0X0/0X30, http://lkml.org/lkml/2007/7/31/580
#fix bad unlock_page() in error case, http://lkml.org/lkml/2007/7/20/168
[global]
bs=8k
iodepth=1024
iodepth_batch=60
randrepeat=1
size=1m
#Use any ext3 for <directory>
directory=<directory>
numjobs=20
[job1]
ioengine=sync
bs=1k
direct=1
rw=randread
filename=file1:file2
[job2]
ioengine=libaio
rw=randwrite
direct=1
filename=file1:file2
[job3]
bs=1k
ioengine=posixaio
rw=randwrite
direct=1
filename=file1:file2
[job4]
ioengine=splice
direct=1
rw=randwrite
filename=file1:file2
[job5]
bs=1k
ioengine=sync
rw=randread
filename=file1:file2
[job7]
ioengine=libaio
rw=randwrite
filename=file1:file2
[job8]
ioengine=posixaio
rw=randwrite
filename=file1:file2
[job9]
ioengine=splice
rw=randwrite
filename=file1:file2
[job10]
ioengine=mmap
rw=randwrite
bs=1k
filename=file1:file2
[job11]
ioengine=mmap
rw=randwrite
direct=1
filename=file1:file2
Thanks,
-Guru
prev parent reply other threads:[~2009-04-24 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 13:22 request for job files Jens Axboe
2009-04-22 16:58 ` Girish Satihal
2009-04-22 17:36 ` Jens Axboe
2009-04-22 20:32 ` Chris Worley
2009-04-23 5:50 ` Jens Axboe
2009-04-23 15:48 ` Chris Worley
2009-04-23 18:34 ` Jens Axboe
2009-04-24 5:00 ` Gurudas Pai [this message]
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=49F14771.6040004@oracle.com \
--to=gurudas.pai@oracle.com \
--cc=fio@vger.kernel.org \
--cc=jens.axboe@oracle.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