linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Tejun Heo <htejun@gmail.com>
Cc: Richard Scobie <richard@sauce.co.nz>, linux-ide@vger.kernel.org
Subject: Re: Resets on sil3124 & sil3726 PMP
Date: Mon, 03 Sep 2007 02:57:24 -0700	[thread overview]
Message-ID: <46DBDA84.3050505@vc.cvut.cz> (raw)
In-Reply-To: <46DBCCE9.9080806@gmail.com>

Tejun Heo wrote:
> Petr Vandrovec wrote:
>> For comparsion 1TB Hitachi behind 3726 PMP (again MS4UM) with sata_sil
>> patch I sent last week (no NCQ, 1.5Gbps link between 3512 and PMP, and
>> 3.0Gbps link between PMP and drive... why is it faster?):
> 
> If you turn off NCQ by echoing 1 to /sys/block/sdd/device/queue_depth on
> sata_sil24, does the performance change?

I have recompiled kernel with all debugging disabled, and it brought me 
1.5MBps, so it is still consistently 1MBps slower than on sil. 
Disabling NCQ seems to improve concurrent access a bit (for which I have 
no explanation), while slows down single drive scenario:

With NCQ:

1TB alone: 81.22, 79.86
1TB+1TB:   56.28+56.70, 53.51+56.11

Without NCQ:

1TB alone: 79.78, 80.82
1TB+1TB:   57.99+58.12, 56.50+56.46

3512 sil, no NCQ:

1TB alone: 82.28, 82.18
1TB+1TB:   47.20+47.54    # Here apparently command based switching or 
1.5Gbps link between device and PMP becomes bottleneck

And it seems that I observe what other poster pointed out - that 
apparently all SiI chips are limited somewhere around 120-130MBps, and 
cannot do more even if you pretty ask...
							Petr


  reply	other threads:[~2007-09-03  9:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27  4:55 Resets on sil3124 & sil3726 PMP Richard Scobie
2007-08-27  7:11 ` Petr Vandrovec
2007-09-03  8:59   ` Tejun Heo
2007-09-03  9:57     ` Petr Vandrovec [this message]
2007-09-03 12:50       ` Tejun Heo
2007-09-04  1:38         ` Petr Vandrovec
2007-09-05 12:08           ` Petr Vandrovec
2007-09-05 21:30             ` Robin H. Johnson
2007-09-06  9:52               ` Petr Vandrovec
2007-09-06 18:02                 ` Tejun Heo
2007-09-06 17:59             ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2007-09-03 19:39 Richard Scobie
2007-09-03 20:34 ` Robin H. Johnson
2007-09-03 21:21   ` Richard Scobie
2007-08-27  8:08 Richard Scobie
2007-08-27 22:49 ` Robin H. Johnson
2007-08-15 13:58 Rusty Conover
2007-08-17 18:06 ` Tejun Heo
2007-08-20 19:56   ` Rusty Conover
2007-08-21  2:42     ` Rusty Conover
2007-08-22  3:03       ` Tejun Heo
2007-08-22  5:00         ` Rusty Conover
2007-08-22  5:43           ` Tejun Heo
2007-08-22  6:11             ` Rusty Conover
2007-08-22  6:39               ` Tejun Heo
2007-08-22  6:56                 ` Rusty Conover
2007-08-22  7:02                   ` Tejun Heo
2007-08-22  7:49                     ` Rusty Conover
2007-08-25  2:19                       ` Tejun Heo
2007-08-26 16:37                         ` Rusty Conover
2007-08-27  1:18                           ` Tejun Heo
2007-08-14 23:39 Rusty Conover
2007-08-15  6:10 ` Tejun Heo

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=46DBDA84.3050505@vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=richard@sauce.co.nz \
    /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).