From: Tobias Reinhard <tracer@robotech.de>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with concurrent SATA-Writes
Date: Tue, 31 May 2005 21:49:58 +0200 [thread overview]
Message-ID: <429CBFE6.7030107@robotech.de> (raw)
In-Reply-To: <20050531190008.GJ23621@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
> Might it be a problem with having two things using /dev/zero at the same
> time?
No, dding from /dev/zero two times at the same time is working perfectly
> What blocksize do you use with dd?
Generally I use 1M. But the Problem is the same with 128k or with 4k
> What happens if you do dd from /dev/zero to two different files on one
> of the hds (with some filesystem on the drive obviously)?
I did it without a FS on it and its no problem to write at two different
locations - as long as they are on one disc.
It seems to me that the driver has problems with handling two
write-requests on two ports at the same time.
Tobias
next prev parent reply other threads:[~2005-05-31 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 17:16 Problem with concurrent SATA-Writes Tobias Reinhard
2005-05-31 19:00 ` Lennart Sorensen
2005-05-31 19:49 ` Tobias Reinhard [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-27 16:12 Tobias Reinhard
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=429CBFE6.7030107@robotech.de \
--to=tracer@robotech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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