From: Jens Axboe <axboe@kernel.dk>
To: "Ruvinsky, Konstantin" <Konstantin.Ruvinsky@emc.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: The problem of blocks overwriting by multiple writers for raw devices
Date: Tue, 25 Jun 2013 10:01:52 +0200 [thread overview]
Message-ID: <20130625080152.GB13354@kernel.dk> (raw)
In-Reply-To: <EEF9E3C12F20174DA289A981D6CCA6C832466199B3@MX44A.corp.emc.com>
On Fri, Jun 21 2013, Ruvinsky, Konstantin wrote:
> Hi Jens,
>
> Question/suggestion (I am almost sure that it was already discussed
> here, but maybe ...):
>
> Why not to divide a raw device size for multithreaded write by number
> of threads and let every thread to write on a separate chunk (as you
> do for FS - every thread writes to a separate file)? This will solves
> the problem of blocks overwriting by multiple writers.
You can do that manually, using zones for instance. Fio tries not to
guess what you are trying to do. It'll just do what you ask it to.
--
Jens Axboe
prev parent reply other threads:[~2013-06-25 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 13:37 The problem of blocks overwriting by multiple writers for raw devices Ruvinsky, Konstantin
2013-06-25 8:01 ` 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=20130625080152.GB13354@kernel.dk \
--to=axboe@kernel.dk \
--cc=Konstantin.Ruvinsky@emc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox