From: mru@users.sourceforge.net (Måns Rullgård)
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DMA transfers in 2.5.67
Date: 16 Apr 2003 12:11:02 +0200 [thread overview]
Message-ID: <yw1x1y02eoqx.fsf@zaphod.guide> (raw)
In-Reply-To: <20030416140110.A642@jurassic.park.msu.ru>
Ivan Kokshaysky <ink@jurassic.park.msu.ru> writes:
> > I set the latency to 128 using setpci and now I get 66 MB/s. Other
> > values give slower transfer rates. Is there some other setting that
> > could improve it even more?
>
> Interesting. Did you set latency 128 for all devices or only for
> 3Dlabs card?
Only the 3Dlabs. The remaining cards are configured like this:
00:05.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] (rev 78)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
Flags: bus master, medium devsel, latency 64, IRQ 25
00:06.0 Display controller: 3DLabs GLINT R3 (rev 01)
Subsystem: 3DLabs: Unknown device 0121
Flags: bus master, 66Mhz, medium devsel, latency 128, IRQ 27
00:07.0 RAID bus controller: Triones Technologies, Inc.: Unknown device 0008 (rev 07)
Subsystem: Triones Technologies, Inc.: Unknown device 0001
Flags: bus master, 66Mhz, medium devsel, latency 120, IRQ 26
00:07.1 RAID bus controller: Triones Technologies, Inc.: Unknown device 0008 (rev 07)
Subsystem: Triones Technologies, Inc.: Unknown device 0001
Flags: bus master, 66Mhz, medium devsel, latency 120, IRQ 26
00:08.1 IDE interface: Contaq Microsystems 82c693 (prog-if 80 [Master])
Flags: bus master, medium devsel, latency 0
00:08.2 IDE interface: Contaq Microsystems 82c693 (prog-if 00 [])
Flags: bus master, medium devsel, latency 0
00:08.3 USB Controller: Contaq Microsystems 82c693 (prog-if 10 [OHCI])
Flags: bus master, medium devsel, latency 0
00:09.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
Subsystem: Adaptec: Unknown device 0035
Flags: bus master, medium devsel, latency 64, IRQ 24
00:09.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
Subsystem: Adaptec: Unknown device 0035
Flags: bus master, medium devsel, latency 64, IRQ 28
00:09.2 USB Controller: NEC Corporation: Unknown device 00e0 (rev 02) (prog-if 20)
Subsystem: Adaptec: Unknown device 00e0
Flags: bus master, medium devsel, latency 68, IRQ 32
As you can see, the good IDE controller (Triones/Highpoint hpt374) has
a latency of 120. Disk transfer rates are still only half of what I
get with a 2.4 kernel. What could be the cause of this?
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-04-16 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 20:01 Måns Rullgård
2003-04-15 20:31 ` Alan Cox
2003-04-15 21:38 ` Måns Rullgård
2003-04-15 20:48 ` Alan Cox
2003-04-15 22:09 ` Måns Rullgård
2003-04-16 8:36 ` Ivan Kokshaysky
2003-04-16 8:43 ` Måns Rullgård
2003-04-16 8:59 ` Måns Rullgård
2003-04-16 9:30 ` Måns Rullgård
2003-04-16 10:01 ` Ivan Kokshaysky
2003-04-16 10:11 ` Måns Rullgård [this message]
2003-04-16 9:45 Chuck Ebbert
2003-04-16 10:11 ` Andrew Morton
2003-04-16 10:13 ` Andrew Morton
2003-04-16 10:13 ` Måns Rullgård
2003-04-18 11:25 Chuck Ebbert
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=yw1x1y02eoqx.fsf@zaphod.guide \
--to=mru@users.sourceforge.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ink@jurassic.park.msu.ru \
--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®