linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Denys Dmytriyenko <denis@denix.org>
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: Thu, 06 Mar 2008 16:08:48 +0900	[thread overview]
Message-ID: <47CF9880.4080900@gmail.com> (raw)
In-Reply-To: <20080306065513.GE7150@denix.org>

Denys Dmytriyenko wrote:
>>> Also, few months ago instead of sata_sil24 I had my drives connected to
>>> sata_mv (Supermicro 8-port) and performance was normal...
>> Everything seems okay.  I wonder where the difference is.  Does "dd
>> if=/dev/zero of=file oflags=direct bs=1M" make any difference?  And can
>> you vacate a raw partition and try it on there?
> 
> oflag=direct has no effect - same speed. Tried it on a raw /dev/sda device
> and still no difference. It maybe slighly better, giving me 18 MB/s.
> 
> Can it be something with the way SiI 3124 controller is configured in the
> system?

Hmmm... That's strange you did specify the "bs" parameter, right?  It
should essentially give the same performance as "hdparm -t".  I wonder
where the difference comes from.

-- 
tejun

  reply	other threads:[~2008-03-06  7:08 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
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 [this message]
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=47CF9880.4080900@gmail.com \
    --to=htejun@gmail.com \
    --cc=FUNK.Gabor@hunetkft.hu \
    --cc=denis@denix.org \
    --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).