From: Mauk van der Laan <mauk.lists@maatwerk.net>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: siimage slow on 2.4.21-rc6-ac2
Date: Wed, 04 Jun 2003 03:23:06 +0200 [thread overview]
Message-ID: <3EDD49FA.2080407@maatwerk.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10306031746070.27756-100000@master.linux-ide.org>
He is right. I did several tests and it is the max_kb setting
that does it, not the fact that I programmed both disks.
Sorry to have put you in the wrong direction.
By the way, the autodma code doesnt seem to do anything?
Mauk
Andre Hedrick wrote:
>NO, it is not irrelevant.
>
>Seagate and Silicon Image are the only two player (well intel now) who did
>their own PHY. They did not use the Marvel pairs.
>
>It is a function of possible ECC on the wire and the relation to the
>segments in the PIO or SG operations. It is a FIFO issue based on 512byte
>boundaries being breached on corner cases.
>
>The data on the wire is in 8K units.
>
>It is a 7.5K + 0.5K corner case.
>
>max_kb_per_request:15 == 7.5K
>
>This prevents this corner case until I can code the proper special case SG
>table.
>
>drive->id->hwconfig |= 0x6000;
>
>Is needed to fake the driver for device side cable detect.
>There are several issues and I have not had time to keep up.
>
>I have to do other business ventures because being an independent
>developer/contract no longer can pay the bills. More proof that free
>drivers and free software still has a cost to somebody.
>
>Cheers,
>
>On 3 Jun 2003, Alan Cox wrote:
>
>
>
>>On Maw, 2003-06-03 at 23:48, Mauk van der Laan wrote:
>>
>>
>>>He! I just did
>>>
>>># hdparm -d1 -X66 /dev/hdX
>>># echo "max_kb_per_request:15" > /proc/.ide/hdX/settings
>>>
>>>on BOTH sata drives and everything works fine!
>>>Is it possible that they influence each other?
>>>
>>>
>>Not as I understand it, but this is rather useful information. The SI
>>does have some ties for PIO mode but not UDMA clocking. This is most
>>interesting information.
>>
>>The max_kb_per thing should be irrelevant btw.
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>>
>
>Andre Hedrick
>LAD Storage Consulting Group
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2003-06-04 1:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 22:09 Mauk van der Laan
2003-06-03 21:22 ` Alan Cox
2003-06-03 22:34 ` Mauk van der Laan
2003-06-03 22:48 ` Mauk van der Laan
2003-06-03 22:19 ` Alan Cox
2003-06-04 0:53 ` Andre Hedrick
2003-06-04 1:23 ` Mauk van der Laan [this message]
2003-06-04 1:21 ` Andre Hedrick
2003-06-04 10:29 ` Alan Cox
2003-06-04 11:05 ` Alan Cox
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=3EDD49FA.2080407@maatwerk.net \
--to=mauk.lists@maatwerk.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®