Flexible I/O Tester development
 help / color / mirror / Atom feed
From: "Neto, Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@netapp.com>
To: Jens Axboe <axboe@kernel.dk>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: FIO - Client and Server - Suggestion
Date: Tue, 7 Oct 2014 22:09:20 +0000	[thread overview]
Message-ID: <D059DCD3.52059%Antonio.Jose.Rodrigues.Neto@netapp.com> (raw)
In-Reply-To: <543462BE.3000101@kernel.dk>



On 10/7/14, 6:01 PM, "Jens Axboe" <axboe@kernel.dk> wrote:

>On 10/07/2014 03:29 PM, Jens Axboe wrote:
>> On 10/07/2014 11:38 AM, Neto, Antonio Jose Rodrigues wrote:
>>> Hi All,
>>>
>>> This is neto from Brazil
>>>
>>> How are you?
>>>
>>> One small suggestion:
>>>
>>> Running Client and Server architecture on FIO, we need to have all
>>>config
>>> files "locally" to run it.
>>>
>>>
>>> Nossa Senhora:tools neto$ ls
>>> 151 152 fio
>>>
>>>
>>>
>>> Nossa Senhora:tools neto$ ./fio --client 10.61.109.151 151 --client
>>> 10.61.109.152 152
>>> hostname=s2, be=0, 64-bit, os=Linux, arch=x86-64,
>>>fio=fio-2.1.13-31-g15e3,
>>> flags=1
>>> hostname=s1, be=0, 64-bit, os=Linux, arch=x86-64,
>>>fio=fio-2.1.13-31-g15e3,
>>> flags=1
>>> <s2> workload: (g=0): rw=read, <s1> workload: (g=0): rw=read,
>>> bs=64K-64K/64K-64K/64K-64K, bs=64K-64K/64K-64K/64K-64K,
>>>ioengine=libaio,
>>> iodepth=1
>>> ioengine=libaio, iodepth=1
>>>
>>> If we are doing a test in an HPC environment with hundred of files,
>>> wouldn't be easier to try to point to a single location for the file
>>>and
>>> access it remotely (we won't need to copy it locally).
>>>
>>>
>>> For example:
>>>
>>> ./fio --client 10.61.109.151 --remote-config /root/fio/151 --client
>>> 10.61.109.152 --remote-config /root/fio/152
>>>
>>>
>>> Thoughts?
>> 
>> That's a good idea, would not be hard to insert that step of having the
>> remote fio server load a local config file. I'll look into that.
>
>Totally untested, but the below is a start. On the client side, you'd do:
>
>fio --client=server-hostname --remote-config /some/path/to/file
>
>and then the server should attempt to open that. Needs a bit of error
>handling, but the concept should be there.
>
>-- 
>Jens Axboe


Hi Jens,

This is neto from Brazil

How are you?

I think it is not working.... Please see below:

Nossa Senhora:fio.patch neto$ ./fio --client 10.61.109.151 --remote-config
/root/fio.patch/model
hostname=s1, be=0, 64-bit, os=Linux, arch=x86-64, fio=fio-2.1.13-31-g15e3,
flags=1

Thank you,


neto



  reply	other threads:[~2014-10-07 22:09 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 [this message]
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
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=D059DCD3.52059%Antonio.Jose.Rodrigues.Neto@netapp.com \
    --to=antonio.jose.rodrigues.neto@netapp.com \
    --cc=axboe@kernel.dk \
    --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