From: Mark Nelson <mark.a.nelson@gmail.com>
To: fio@vger.kernel.org
Subject: multiple --name parameters with non-file engine?
Date: Mon, 18 Aug 2014 19:42:30 -0500 [thread overview]
Message-ID: <53F29D76.9080108@gmail.com> (raw)
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?
Thanks,
Mark
next reply other threads:[~2014-08-19 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 0:42 Mark Nelson [this message]
2014-08-22 22:23 ` multiple --name parameters with non-file engine? Jens Axboe
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=53F29D76.9080108@gmail.com \
--to=mark.a.nelson@gmail.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 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.