linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tobias Reinhard <tracer@robotech.de>
To: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Problem with concurrent SATA-Writes
Date: Wed, 01 Jun 2005 19:13:06 +0200	[thread overview]
Message-ID: <429DECA2.6020609@robotech.de> (raw)

Hello Jeff, hello to the linux-ide-list!

I already posted this to the lkml, but unfortunately I got no usefull 
answer. I think the problem is related to the SIL-Driver so maybe you 
are the right person to contact - or someone at the linux-ide-list...

If you need any other informations or logs please tell me. I really want 
to use these discs.

Tobias

Original Msg:
--------
I have a problem with two SATA-Discs. I have an onboard SIL3114 with
four SATA-Ports an onboard NVIDIA with two SATA-Ports - both controllers
are disable via BIOS (and are not detected by Linux)(only for this test
of course - normally I have other HDD on this ports). The only
controller that is found is the add-on controller in a PCI-Slot
(SIL3112). And that is the one I have trouble with.

If I read or write  (via dd) from the first one -> no problems. Same
when read or write from the second or when I read (only read!) from both
at the same time. Data-Transfer-Rate is around 45MB/s for each HDD.

The problem occures when I try to write on both discs at the same time.
For example I write /dev/zero to the first one and then start to write
/dev/zero to the second one. The System-Load goes up to 4 with nearly
100% io-wait and nearly no write-access to the drives.

Any hints?

- no errormessages in syslog
- happens with Kernel 2.6.11.7 and with 2.6.12-rc5
- HDDs are Samsung Spinpoint 200GB
- (I use the SCSI-SATA-Drivers)


             reply	other threads:[~2005-06-01 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 17:13 Tobias Reinhard [this message]
2005-06-01 17:33 ` Problem with concurrent SATA-Writes Jeff Garzik
2005-06-01 22:40   ` Tobias Reinhard
2005-06-02 21:57     ` Jeff Garzik

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=429DECA2.6020609@robotech.de \
    --to=tracer@robotech.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).