Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Mark Nelson <mark.a.nelson@gmail.com>, fio@vger.kernel.org
Subject: Re: multiple --name parameters with non-file engine?
Date: Fri, 22 Aug 2014 17:23:02 -0500	[thread overview]
Message-ID: <53F7C2C6.7000703@kernel.dk> (raw)
In-Reply-To: <53F29D76.9080108@gmail.com>

On 2014-08-18 19:42, Mark Nelson wrote:
> Hi Guys,
>
> I'm using the librbd engine and trying to determine what exactly happens
> when multiple --name parameters are passed.  Primarily, I'm wondering if
> each fio process ends up writing to the same blocks on the rbd volume
> during sequential writes.  Looking at the code, I see a note that we
> pretend to deal with files even if the engine doesn't understand the
> concept of files:
>
> https://github.com/axboe/fio/blob/master/engines/rbd.c#L405
> https://github.com/axboe/fio/blob/master/filesetup.c#L1239
>
> I'm not seeing anything (might be missing it) in the rbd engine or there
> that would partition the volume based on the process though.  Am I
> missing anything?

The same thing will happen as if you ran two instances of fio with the 
same options. For rbd, each job will create/connect/open and rbd 
instance. For each of these, you can set the rbd pool and clientname.

-- 
Jens Axboe



  reply	other threads:[~2014-08-22 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19  0:42 multiple --name parameters with non-file engine? Mark Nelson
2014-08-22 22:23 ` Jens Axboe [this message]
2014-08-23  1:45   ` Mark Nelson
2014-08-23  6:17     ` Sitsofe Wheeler

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=53F7C2C6.7000703@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=mark.a.nelson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox