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: Tue, 07 Oct 2014 20:57:55 -0600 [thread overview]
Message-ID: <5434A833.1040702@kernel.dk> (raw)
In-Reply-To: <D05A1880.520B9%Antonio.Jose.Rodrigues.Neto@netapp.com>
On 2014-10-07 20:54, Neto, Antonio Jose Rodrigues wrote:
>
>
> On 10/7/14, 9:53 PM, "Jens Axboe" <axboe@kernel.dk> wrote:
>
>> On 2014-10-07 19:07, Neto, Antonio Jose Rodrigues wrote:
>>> I found what is happening
>>>
>>> If I use a non absolute path it works: the remote config should be on
>>> the
>>> same directory with fio
>>>
>>>
>>> Nossa Senhora:fio.patch neto$ ./fio --client 10.61.109.151
>>> --remote-config
>>> conf3
>>>
>>>
>>>
>>> If I specify an absolute path, it does not work
>>>
>>> Nossa Senhora:fio.patch neto$ ./fio --client 10.61.109.151
>>> --remote-config
>>> /root/fio.patch/conf3
>>> hostname=s1, be=0, 64-bit, os=Linux, arch=x86-64,
>>> fio=fio-2.1.13-31-g15e3,
>>> flags=1
>>>
>>>
>>> Do you think we could fix it to make sure we can use --remote-config
>>> with
>>> an absolute path?
>>
>> That's very odd, there should be nothing special about it. If I do this:
>>
>> axboe@lenny:/home/axboe/git/fio $ stat /root/x.fio
>> stat: cannot stat �/root/x.fio�: Permission denied
>> $ ./fio --client=localhost --remote-config /root/x.fio
>>
>> and run
>>
>> axboe@lenny:/home/axboe/git/fio $ sudo strace -o x -f ./fio --server
>> fio: server listening on 0.0.0.0,8765
>>
>> and then look at the x strace output file, it all looks fine:
>>
>> 28632 recvfrom(4, "\v\0\1\0/root/x.fio", 15, MSG_WAITALL, NULL, NULL) =
>> 15
>> 28632 open("/root/x.fio", O_RDONLY) = 5
>>
>> which is all find and dandy. Fio just passes the string of the filename,
>> and the server just does an fopen on that passed in file. So please run
>> the same experiment on your end with an strace of the server and the
>> arguments you used on the client, I'd like to see that.
>>
>> --
>> Jens Axboe
>>
>
> Hi Jens,
>
> This is neto from Brazil
>
> How are you?
>
> It's very strange....
>
> I have applied the patch again... Make clean, make and it's working now :-(
>
> On linux it's working
>
> But I applied the patch on my mac, but it's not working
>
> Nossa Senhora:fiop neto$ patch < net-remote-config.patch
> (Stripping trailing CRs from patch.)
> patching file client.c
> (Stripping trailing CRs from patch.)
> patching file client.h
> (Stripping trailing CRs from patch.)
> patching file init.c
> (Stripping trailing CRs from patch.)
> patching file server.c
> (Stripping trailing CRs from patch.)
> patching file server.h
>
>
>
> Nossa Senhora:fiop neto$ ./fio --client 10.61.109.151 --remote-config
> /root/fiop/model
> Nossa Senhora:fiop neto$
>
>
>
> Could you please make the changes to github and I will download form
> there. Something is not right here with the patch.
Always ensure that you make clean, might be the same on the mac. In any
case, it's committed, but it a separate branch. So when pulling, you
need to checkout the remote-config branch. Once it's fully done, I will
pull it into the master branch.
--
Jens Axboe
next prev parent reply other threads:[~2014-10-08 2:57 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
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 [this message]
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=5434A833.1040702@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