From: Ben England <bengland@redhat.com>
To: Gurvinder Singh <gurvindersinghdahiya@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
fio@vger.kernel.org, Sitsofe Wheeler <sitsofe@gmail.com>
Subject: Re: client/server test to write to single file from all clients
Date: Sun, 22 May 2016 18:25:39 -0400 (EDT) [thread overview]
Message-ID: <547897333.64878071.1463955939138.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CALjAwxgLWN=teei=LJj7rJHJ8MDSYJJ7i_XHKYkdPq2S9b1efA@mail.gmail.com>
Gurvinder,
you are correct, there is a problem at present getting fio threads on multiple clients to share files using the --client option, because it does insert the IP addr of the client in the pathname. I think the current behavior is a reasonable default behavior - we want "embarrassingly parallel" behavior normally. For example, fio threads within a single client run on separate files by default. But it would be useful to be able to override this and have clients share files - this option would be useful for testing distributed filesystems for example. Perhaps a "--shared-across-clients" option, valid only when --client specified, would be useful in this case? This would just suppress the insertion of IP address into the filename. It should be feasible to do this, if people agree that this is what they want.
Jens' comment about being unable to verify or predict file contents does apply, if writes are done this way. So you wouldn't really have a way to know if your writes or reads succeeded. To make this possible, I suspect fio would need to serialize writes from different clients to the same byte range within a file, I don't know if this can be easily done.
-ben
----- Original Message -----
> From: "Sitsofe Wheeler" <sitsofe@gmail.com>
> To: "Gurvinder Singh" <gurvindersinghdahiya@gmail.com>
> Cc: "Jens Axboe" <axboe@kernel.dk>, fio@vger.kernel.org
> Sent: Tuesday, May 3, 2016 2:18:04 PM
> Subject: Re: client/server test to write to single file from all clients
>
> On 3 May 2016 at 06:34, Gurvinder Singh <gurvindersinghdahiya@gmail.com>
> wrote:
> > Reposting it as gmail android client inserted html and it got rejected
> > from mailing list.
> > -----------------------------
> > Thanks Jens for the reply. As FIO supports writing to same file in
> > client/server mode then what should be filename/filename_pattern should be.
> > As currently specifying filename it appends hostname/IP to file name and
> > thus each client ends up writing to its own file.
>
> Can you post your jobfile here?
>
> --
> Sitsofe | http://sucs.org/~sits/
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-05-22 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 19:11 client/server test to write to single file from all clients Gurvinder Singh
2016-05-03 1:15 ` Jens Axboe
2016-05-03 3:48 ` Gurvinder Singh
2016-05-03 5:34 ` Gurvinder Singh
2016-05-03 18:18 ` Sitsofe Wheeler
2016-05-22 22:25 ` Ben England [this message]
2016-05-23 14:38 ` Jens Axboe
2016-05-23 16:53 ` Gurvinder Singh
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=547897333.64878071.1463955939138.JavaMail.zimbra@redhat.com \
--to=bengland@redhat.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=gurvindersinghdahiya@gmail.com \
--cc=sitsofe@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.