From: Jens Axboe <axboe@kernel.dk>
To: Danny Kukawka <dkukawka@suse.de>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Recent changes
Date: Sat, 14 Apr 2012 16:47:08 +0200 [thread overview]
Message-ID: <4F898DEC.2000807@kernel.dk> (raw)
In-Reply-To: <4F891D18.5020202@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2012-04-14 08:45, Danny Kukawka wrote:
> Am 06.04.2012 19:44, schrieb Jens Axboe:
>> On 2012-04-06 11:40, Danny Kukawka wrote:
>>> Am 06.04.2012 15:31, schrieb Jens Axboe:
>>>> On 2012-04-05 22:29, Danny Kukawka wrote:
>>>>> Am 06.04.2012 06:00, schrieb Jens Axboe:
>>>>>> The following changes since commit 885ac623a4f154007efa49266bb381bcbc60f1e6:
>>>>>>
>>>>>> iolog: remove assert in io_u overlap (2012-04-04 14:11:58 -0600)
>>>>>>
>>>>>> are available in the git repository at:
>>>>>> git://git.kernel.dk/fio.git master
>>>>>>
>>>>>> Jens Axboe (1):
>>>>>> group reporting: fix bad values of min/max
>>>>>
>>>>> Should this fix also the minb/maxb and mint/maxt ? If so, it doesn't
>>>>> work for me.
>>>>>
>>>>> fio --name=fio1-write-4m-rbd --direct=1 --size=50g --group_reporting
>>>>> --bs=4m --rw=write --iodepth=128 --ioengine=libaio --filename=/dev/rbd0
>>>>>
>>>>> still prints:
>>>>>
>>>>> READ: io=65260MB, aggrb=111334KB/s, minb=114006KB/s, maxb=114006KB/s,
>>>>> mint=600232msec, maxt=600232msec
>>>>
>>>> Since that's still off by 1.024, are you absolutely sure you are running
>>>> the right version of fio?
>>
>>> I used git snapshot with latest commit
>>> ddb754dbb54a8174080f753c85ff56a7ffca3957, but I can recheck if needed.
>>
>> Yes, please re-check, it should not be happening and I don't see it
>> here.
>>
>
> I checked again with 8423bd1106a0 and I still see the same problem:
>
> fio --name=fio1-write-4m-rbd --direct=1 --size=50g --group_reporting
> --bs=4m --rw=write --iodepth=128 --ioengine=libaio
> --filename=$TEST_TARGET --output=$DIR/fio1-write-4m-rbd
>
> Run status group 0 (all jobs):
> WRITE: io=51200MB, aggrb=20080KB/s, minb=20080KB/s, maxb=20080KB/s,
> mint=2610946msec, maxt=2610946msec
I'm confused on what you think is an issue? From the above, fio
transferred 51200MB, which is 52428800KB. The runtime was 2610.946s,
which gives us a throughput of 20080.38KB/sec. Which is what fio
reports. aggrb/minb/maxb are identical, which was the original bug.
What am I missing?
- --
Jens Axboe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJPiY3oAAoJEPfTWPspceCm7TIP/jCGLv0L6Th7T4FosTrCC0bm
U9jUDWkNo+b4n+87FLTmX6rxXenNN/NbGYJHaCE8A+FnWyDLihhEAslMD9mqn7OA
66EWir/HrbzikQ6mF9fMPDWCLLNKVV+eVORmrN3Ne6y6d3luH5RiMFKOfWmdbhv2
cHhVpDx5hfGF+tvRcPy/NIOkl7gNszOqF2ili9wP+aTokp+2jF7rVK9pw7KfA9jG
IPrt2oC6hIr6+6v8xekZRgEH61R/Gsq6T0Tf0dJtEMMNhcspEpXZbKCf1xV8+22W
HmYsjVJysIPEn0KCnPzE+DtDEF/rInbYvlTuOcJS1ugMt/AGOWtQm9OprIQTQsc+
T0lMQ4lVEzxmcvy3dMs2pnTL0pdWOAVfNXGopVpd1jV0jI1uBvsZyW2sBpiVn7nA
10GB6Y97Cm+ap9oaP+nnxRgLjmHrDpbgSFnRt6CFUnD+6xp2iV8Bo7qA06e0ABwT
IFpeHW57OhhR+zIMqNqsldvsuuPB8PKWxvi0eH7YBuDKk/XoD91Im9iYJRxjbvBQ
xN7hpjeWFQap4OLPERKDoTYBcJ4NdYaM9UdXPsmazc4T28K2tmxtzcIrkalj1Ryn
d6B0FoQRWZlPYk3c7NbDKcz49llC08zdptNffMP2g8fKzgGxzTY/oAgiET6JqK/o
dSMKbZgMjfK2iNGUjLR9
=Mpll
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-04-14 14:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120406040004.1BF99484001@kernel.dk>
2012-04-06 4:29 ` Recent changes Danny Kukawka
2012-04-06 13:31 ` Jens Axboe
2012-04-06 17:40 ` Danny Kukawka
2012-04-06 17:44 ` Jens Axboe
2012-04-14 6:45 ` Danny Kukawka
2012-04-14 14:47 ` Jens Axboe [this message]
2011-10-14 4:00 Jens Axboe
[not found] <20110125050003.F378B37A302@kernel.dk>
2011-01-27 21:08 ` Steven Pratt
2011-01-27 21:12 ` Jens Axboe
2011-01-27 22:06 ` Bruce Cran
2011-01-28 8:28 ` Jens Axboe
[not found] <20110127050004.1AE9737A304@kernel.dk>
2011-01-27 8:51 ` Bruce Cran
2011-01-27 9:08 ` Jens Axboe
[not found] <20110114050004.0ECBF37A2F4@kernel.dk>
2011-01-14 11:38 ` Bruce Cran
2011-01-14 11:41 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2010-11-06 5:00 Jens Axboe
[not found] <869776.96350.qm@web63807.mail.re1.yahoo.com>
2009-04-24 4:40 ` Gurudas Pai
[not found] <20090409040002.0D18237A271@kernel.dk>
2009-04-17 21:38 ` Girish Satihal
2009-04-18 17:48 ` Jens Axboe
2009-04-20 14:42 ` Girish Satihal
2009-04-20 18:05 ` Jens Axboe
2009-04-20 20:54 ` Girish Satihal
2009-04-21 5:28 ` Jens Axboe
2009-04-21 7:47 ` Jens Axboe
2009-04-21 15:46 ` Girish Satihal
2009-04-21 19:15 ` Jens Axboe
2009-04-21 22:17 ` Girish Satihal
2009-04-22 5:46 ` Jens Axboe
2009-04-22 5:53 ` Gurudas Pai
2009-04-22 16:46 ` Girish Satihal
2009-04-22 17:40 ` Jens Axboe
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=4F898DEC.2000807@kernel.dk \
--to=axboe@kernel.dk \
--cc=dkukawka@suse.de \
--cc=fio@vger.kernel.org \
/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