From: "Richard W.M. Jones" <rjones@redhat.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: fio <fio@vger.kernel.org>, eblake@redhat.com, nbd@other.debian.org
Subject: Re: [PATCH fio] engines: Add Network Block Device (NBD) support.
Date: Fri, 19 Apr 2019 10:40:34 +0100 [thread overview]
Message-ID: <20190419094034.GB3926@redhat.com> (raw)
In-Reply-To: <CALjAwxgWho3m5V+xgSH0U8uEe=z9icHo8VXT4U3V3njOvCuT7Q@mail.gmail.com>
On Fri, Apr 19, 2019 at 10:27:49AM +0100, Sitsofe Wheeler wrote:
> On Thu, 18 Apr 2019 at 15:10, Richard W.M. Jones <rjones@redhat.com> wrote:
> > If there are multiple jobs (files?) should these be striped over the
> > block device?
>
> It depends on how you define the job. If you were to just copy the job
> and give it a new name it would likely just overlap the first job
> (because it's just going to do the same thing at the same time). You
> would need to use something like numjobs
> (https://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-numjobs
> ) offset_increment
> (https://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-offset-increment
> ) and a workload that skipped (e.g. rw=write:12k -
> https://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-readwrite
> ) to achieve striping.
I meant should the NBD engine stripe the jobs. Something like: job 0
gets to use the first <size> bytes of the NBD device, job 1 gets to us
the next <size> bytes, etc. (Or actually striped/interleaved using a
smaller block size). In other words it would be something hidden
inside the NBD engine and not "visible" to fio.
Thanks for the rest of the email - very helpful.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
next prev parent reply other threads:[~2019-04-19 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 14:09 [PATCH fio] engines: Add Network Block Device (NBD) support Richard W.M. Jones
2019-04-18 14:09 ` Richard W.M. Jones
2019-04-19 15:28 ` Elliott, Robert (Servers)
2019-04-19 9:27 ` Sitsofe Wheeler
2019-04-19 9:40 ` Richard W.M. Jones [this message]
2019-04-19 9:51 ` 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=20190419094034.GB3926@redhat.com \
--to=rjones@redhat.com \
--cc=eblake@redhat.com \
--cc=fio@vger.kernel.org \
--cc=nbd@other.debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox