From: "Frank D'Arcy" <frank.darcy@s3group.com>
To: fio@vger.kernel.org
Subject: using fio client on 64-bit machine with fio server on 32-bit machine
Date: Fri, 27 Jun 2014 08:00:31 +0100 [thread overview]
Message-ID: <53AD168F.3070403@s3group.com> (raw)
Hi,
I've been playing around with fio (which is really great thanks)
with a view to testing hard disks on set-top boxes (which I don't have yet)
and as prep for this I created a test environment consisting of
2 x virtual machines running 32-bit ubuntu (using "hashicorp/precise32"
from vagrant cloud)
running on a 64-bit machine with ubuntu 12.04.
I started fio (v2.1.10) running in server mode on both virtual machines
as follows
$ fio --server=,8880
and launched 2 fio (v2.1.10) instances in client mode on the host 64-bit
machine,
$ fio --client=ip:127.0.0.1,8882 test.fio
$ fio --client=ip:127.0.0.1,8881 test.fio
where ports 8881 and 8882 are forwarded to port 8880 on each VM
The sample test.fio (below) runs for 25 seconds
but the values printed by the clients look garbled.
eg. runtime is a huge number ("runt= 107374182400000msec")
Same issue is seen when I switched to using latest fio from "git clone"
and the same issue is seen with all output formats (json, terse, normal)
I changed one of the virtual machines to 64-bit ubuntu (using
"hashicorp/precise64" from vagrant cloud)
and the client talking to the fio server on that VM gave the correct
results (eg. "runt= 25001msec")
while the client talking to the 32-bit ubuntu VM continued to show
garbled values.
So it looks like support is not there for client-server setups on
non-matching architectures ?
eg. 32-bit client to 64-bit server in this case,
and perhaps endianess differences would be a problem too? ( but I
haven't tried that )
Apologies if I've missed this issue raised elsewhere, I did a quick
search and found no mention of it.
It's not critical for us, as the simple workaround is to run fio
standalone on each set-top box
outputting results to a file and pulling the file back to a central
machine for parsing.
Just wanted to raise it if its unknown to you.
Thanks very much,
Frank
my test ....
[global]
;run for 25 seconds
runtime=25
time_based=1
;directory in which to create files
directory=.
size=1024k
log_avg_msec=500
[job1]
name=job1_stb1
description=Job1 Description
rw=read
blocksize=2
rate=1k
write_bw_log=job1_stb1
write_lat_log=job1_stb1
write_iops_log=job1_stb1
[job2]
name=job2_stb1
description=Job2 Description
rw=write
blocksize=2
rate=500
write_bw_log=job2_stb1
write_lat_log=job2_stb1
write_iops_log=job2_stb1
--
Frank D'Arcy
S3 Group Ltd. South County Business Park, Leopardstown, Dublin 18, Ireland
Visit S3 website: www.s3group.com
-----
The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s). Please direct any additional queries to: communications@s3group.com. Thank You. Silicon and Software Systems Limited (S3 Group). Registered in Ireland no. 378073. Registered Office: South County Business Park, Leopardstown, Dublin 18.
next reply other threads:[~2014-06-27 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 7:00 Frank D'Arcy [this message]
2014-06-27 16:47 ` using fio client on 64-bit machine with fio server on 32-bit machine Jens Axboe
2014-06-27 21:02 ` Jens Axboe
2014-06-30 11:09 ` Frank D'Arcy
2014-06-30 14:52 ` Jens Axboe
2014-06-30 17:06 ` Frank D'Arcy
2014-07-01 2:23 ` 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=53AD168F.3070403@s3group.com \
--to=frank.darcy@s3group.com \
--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