Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] Document that write_iolog is unsafe for concurrent jobs
Date: Sat, 8 Jan 2011 20:26:48 +0100	[thread overview]
Message-ID: <4D28BA78.60807@fusionio.com> (raw)
In-Reply-To: <1294312426-3121-1-git-send-email-stefanha@linux.vnet.ibm.com>

On 2011-01-06 12:13, Stefan Hajnoczi wrote:
> The write_iolog parameter should not be used in the global section since
> each job will independently write to the same file.  The output will be
> interspersed and the file will be corrupt.
> 
> Document that each job should write to its own iolog file.  This will
> save users time when trying out the iolog feature for the first time.

Thanks, I added this and also updated the man page.


-- 
Jens Axboe


      reply	other threads:[~2011-01-08 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 11:13 [PATCH] Document that write_iolog is unsafe for concurrent jobs Stefan Hajnoczi
2011-01-08 19:26 ` Jens Axboe [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=4D28BA78.60807@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=fio@vger.kernel.org \
    --cc=stefanha@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox