From: Jens Axboe <axboe@kernel.dk>
To: "Neto, Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@netapp.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: FIO - Client and Server - Suggestion
Date: Sun, 12 Oct 2014 13:12:48 -0600 [thread overview]
Message-ID: <543AD2B0.2070307@kernel.dk> (raw)
In-Reply-To: <D06015CE.528F5%Antonio.Jose.Rodrigues.Neto@netapp.com>
On 2014-10-12 09:26, Neto, Antonio Jose Rodrigues wrote:
> Just applied the patch and it's perfect.
>
> Please see below:
>
> Nossa Senhora:fiop neto$ ./fio --client 10.61.109.151 --remote-config
> /root/fiop/iotest --client 10.61.109.152 --remote-config /root/fio/iotest
> hostname=s2, be=0, 64-bit, os=Linux, arch=x86-64,
> fio=fio-2.1.13-59-gaa7bc, flags=1
> hostname=s1, be=0, 64-bit, os=Linux, arch=x86-64,
> fio=fio-2.1.13-59-gaa7bc, flags=1
> <s2> fio: unable to open '/root/fio/iotest' job file
> <s1> workload: (g=0): rw=write, bs=32K-32K/32K-32K/32K-32K,
> ioengine=libaio, iodepth=4
> <s1> ...
> <s1> Starting 64 threads
> Jobs: 64 (f=1024): [W(64)] [43.3% done] [882.5M/0K/0K /s] [27.6K/0/0 iops]
> [eta 00m:34s]
Great, at least that took care of that issue. As to missing output from
one client, I've seen that here before, I will look into that. It's a
separate issue.
--
Jens Axboe
next prev parent reply other threads:[~2014-10-12 19:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 17:38 FIO - Client and Server - Suggestion Neto, Antonio Jose Rodrigues
2014-10-07 21:29 ` Jens Axboe
2014-10-07 22:01 ` Jens Axboe
2014-10-07 22:09 ` Neto, Antonio Jose Rodrigues
2014-10-07 22:11 ` Neto, Antonio Jose Rodrigues
2014-10-07 22:34 ` Jens Axboe
2014-10-07 22:44 ` Neto, Antonio Jose Rodrigues
2014-10-08 1:07 ` Neto, Antonio Jose Rodrigues
2014-10-08 1:19 ` Neto, Antonio Jose Rodrigues
2014-10-08 1:58 ` Jens Axboe
2014-10-08 3:24 ` Neto, Antonio Jose Rodrigues
2014-10-08 4:03 ` Jens Axboe
2014-10-08 14:13 ` Neto, Antonio Jose Rodrigues
2014-10-08 14:33 ` Jens Axboe
2014-10-08 14:47 ` Neto, Antonio Jose Rodrigues
2014-10-08 14:52 ` Jens Axboe
2014-10-10 13:32 ` Neto, Antonio Jose Rodrigues
2014-10-11 16:28 ` Jens Axboe
2014-10-11 16:29 ` Neto, Antonio Jose Rodrigues
2014-10-11 16:30 ` Jens Axboe
2014-10-12 15:26 ` Neto, Antonio Jose Rodrigues
2014-10-12 15:33 ` Neto, Antonio Jose Rodrigues
2014-10-12 19:12 ` Jens Axboe [this message]
2014-10-12 19:22 ` Neto, Antonio Jose Rodrigues
2014-10-12 19:27 ` Jens Axboe
2014-10-12 20:28 ` Neto, Antonio Jose Rodrigues
2014-10-13 0:27 ` Jens Axboe
2014-10-13 1:09 ` Neto, Antonio Jose Rodrigues
2014-10-13 13:37 ` Neto, Antonio Jose Rodrigues
2014-10-13 14:37 ` Jens Axboe
2014-10-13 16:10 ` Jens Axboe
2014-10-13 18:29 ` Neto, Antonio Jose Rodrigues
2014-10-13 20:20 ` Jens Axboe
2014-10-08 1:53 ` Jens Axboe
2014-10-08 1:55 ` Jens Axboe
2014-10-08 2:54 ` Neto, Antonio Jose Rodrigues
2014-10-08 2:57 ` Jens Axboe
2014-10-08 3:08 ` Neto, Antonio Jose Rodrigues
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=543AD2B0.2070307@kernel.dk \
--to=axboe@kernel.dk \
--cc=Antonio.Jose.Rodrigues.Neto@netapp.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