From: Michael Weinrich <micxer@micxer.de>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Testing write master and multiple read clients on NFS share
Date: Sun, 24 May 2015 22:50:28 +0200 [thread overview]
Message-ID: <55623994.5020208@micxer.de> (raw)
In-Reply-To: <55612636.4000504@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
Well, as I wrote it was a first try but since it seems to have no
obvious flaws and I was satisfied with the results, I'm happy to have
provided a useful example. Please go ahead and add it if you like.
However I would add the time_based option as Daniel Abuggie suggested.
It made more sense.
I also like the idea to have a bunch of example files since the HOWTO is
very detailed but also very heavy for a beginner to work through.
-- Michael
Am 24.05.15 um 03:15 schrieb Jens Axboe:
> On 05/20/2015 05:51 AM, Michael Weinrich wrote:
>> Yeah, well, I needed a process that writes to the same files the others
>> are reading from to somehow simulate expiring local caches (and to see,
>> if NFS handles that the right way). And yes, it took me quite some time
>> to dig through most of the options to tailor the tests to my needs
>>
>> But I'm also glad to hear, that it doesn't look completely wrong for a
>> first try :-)
>
> I think it looks very reasonable. I'd like to include your job file in
> the examples/ directory, if that's OK with you.
>
> In general, I'd love to have a richer repository of job files included
> (or available, at least). It's much easier for new users to find
> something roughly like what they want and then modify it, than it is to
> start from scratch.
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4213 bytes --]
prev parent reply other threads:[~2015-05-24 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 22:09 Testing write master and multiple read clients on NFS share Michael Weinrich
2015-05-16 11:46 ` Sitsofe Wheeler
2015-05-17 20:55 ` Michael Weinrich
2015-05-20 9:03 ` Sitsofe Wheeler
2015-05-20 11:51 ` Michael Weinrich
2015-05-22 0:06 ` danielabuggie .
2015-05-24 1:15 ` Jens Axboe
2015-05-24 20:50 ` Michael Weinrich [this message]
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=55623994.5020208@micxer.de \
--to=micxer@micxer.de \
--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 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.