linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Gabor FUNK <FUNK.Gabor@hunetkft.hu>,
	linux-ide@vger.kernel.org, Jim Paris <jim@jtan.com>,
	Mark Lord <liml@rtr.ca>
Subject: Re: sata_sil24 stability and performance
Date: Tue, 04 Mar 2008 01:29:43 -0500	[thread overview]
Message-ID: <20080304062942.GA14335@denix.org> (raw)
In-Reply-To: <47CCC1C6.5010600@gmail.com>

On Tue, Mar 04, 2008 at 12:28:06PM +0900, Tejun Heo wrote:
> > I am pretty much convinced at this point that my exceptions/resetting
> > problem is due to the PSU. I've been testing different configurations
> > lately and was able to get stable system powering 14 (!) drives by both
> > PSUs together. The limiting factor is Amps on a single +12V rail:
> > Coolermaster 750 limits single rail to 19A (6 drives @ 2.8A/drive) and
> > my old Enermax 550 has 24A limit (8 drives @ 2.8A/drive). Even though
> > Coolermaster 750 has 4 rails, the wiring is not optimal and only 1 rail
> > is available for the hard drives...
> > 
> > See item #8 here:
> > http://www.pcpower.com/technology/myths/
> 
> Ah... yeah, that's what I've been saying all along.  Fancy powers w/
> multiple 12v rails suck for storage array.  My 15$ no name single lane
> PSU works much better than 40$ dual lane one.

I've got the first exception (but not reset) in several days running in
the above configuration:

Mar  3 19:09:04 [kernel] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar  3 19:09:04 [kernel] ata1.00: irq_stat 0x00020002, device error via D2H FIS
Mar  3 19:09:04 [kernel] ata1.00: cmd ef/42:fe:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 0
Mar  3 19:09:04 [kernel]          res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
Mar  3 19:09:04 [kernel] ata1.00: configured for UDMA/100
Mar  3 19:09:04 [kernel] ata1: EH complete
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Write Protect is off
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Is it something I should be worried about?

> > Tejun,
> > 
> > As one of the Gurus on this list, can you suggest any tweaks/settings
> > to try out to improve/resolve my 17 MB/s write speed limit?
> 
> How did you test?  W/ dd?  hdparm?

# hdparm -t /dev/sda

/dev/sda:
 Timing buffered disk reads:  170 MB in  3.03 seconds =  56.16 MB/sec

# dd if=/dev/zero of=file bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 117.053 s, 17.9 MB/s

# dd if=file of=file1 bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 161.721 s, 13.0 MB/s

# dd if=file of=/dev/null bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 34.6141 s, 60.6 MB/s

A similar drive in an ICH7 box shows more consistent results:

# hdparm -t /dev/sda

/dev/sda:
 Timing buffered disk reads:  182 MB in  3.01 seconds =  60.48 MB/sec

# dd if=/dev/zero of=file bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 242.908 s, 43.2 MB/s

# dd if=file of=/dev/null bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 211.132 s, 49.7 MB/s

Please let me know if you need more details/logs. Thanks in advance!

Regards,
Denys

  reply	other threads:[~2008-03-04  6:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19  2:09 sata_sil24 stability and performance Denys Dmytriyenko
2008-02-19  4:36 ` Jim Paris
2008-02-19  6:39   ` Denys Dmytriyenko
2008-02-19 15:32   ` Mark Lord
2008-03-02  6:14     ` Denys Dmytriyenko
2008-03-02  9:39       ` Gabor FUNK
2008-03-04  0:02         ` Tejun Heo
2008-03-04  0:22           ` Denys Dmytriyenko
2008-03-04  3:28             ` Tejun Heo
2008-03-04  6:29               ` Denys Dmytriyenko [this message]
2008-03-05  8:11                 ` Tejun Heo
2008-03-06  4:14                   ` Denys Dmytriyenko
2008-03-06  4:25                     ` Tejun Heo
2008-03-06  6:55                       ` Denys Dmytriyenko
2008-03-06  7:08                         ` Tejun Heo
2008-03-15 21:43                           ` Denys Dmytriyenko
2008-03-17  3:09                             ` Mark Lord
2008-03-18  0:15                               ` Denys Dmytriyenko
2008-03-18  4:09                                 ` Tejun Heo
2008-03-18  4:53                                   ` Denys Dmytriyenko
2008-03-18  6:40                                     ` Tejun Heo
2008-03-20 22:37                                       ` Denys Dmytriyenko
2008-03-21  0:18                                         ` Tejun Heo
2008-04-14  1:19                                           ` Denys Dmytriyenko
2008-04-14  2:49                                             ` Tejun Heo
2008-04-14 10:55                                             ` Gabor FUNK
2008-03-18  9:14                                     ` Gabor FUNK
2008-03-18 13:06                                       ` Gabor FUNK
2008-03-18 20:05                                   ` Mark Lord
2008-03-18 20:06                                     ` Mark Lord

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=20080304062942.GA14335@denix.org \
    --to=denis@denix.org \
    --cc=FUNK.Gabor@hunetkft.hu \
    --cc=htejun@gmail.com \
    --cc=jim@jtan.com \
    --cc=liml@rtr.ca \
    --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).