* The problem of blocks overwriting by multiple writers for raw devices
@ 2013-06-21 13:37 Ruvinsky, Konstantin
2013-06-25 8:01 ` Jens Axboe
0 siblings, 1 reply; 2+ messages in thread
From: Ruvinsky, Konstantin @ 2013-06-21 13:37 UTC (permalink / raw)
To: fio@vger.kernel.org
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.
Thank you
Konstantin
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: The problem of blocks overwriting by multiple writers for raw devices
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
0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2013-06-25 8:01 UTC (permalink / raw)
To: Ruvinsky, Konstantin; +Cc: fio@vger.kernel.org
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-06-25 8:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox