mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 11:30:43 +0200	[thread overview]
Message-ID: <yw1x65peeqm4.fsf@zaphod.guide> (raw)
In-Reply-To: <yw1xadeqes1s.fsf@zaphod.guide>

mru@users.sourceforge.net (Måns Rullgård) writes:

> > > > Btw, I just noticed that hard disk throughput is much lower with 2.5
> > > > than 2.4.  With 2.4.21-pre5 I get ~40 MB/s, but with 2.5.67 the speed
> > > > drops to 25-30 MB/s.  Everything according to hdparm.  Is it possible
> > > > that DMA is generally slow for some reason?
> > > 
> > > Possible reason is that in 2.4 we've forced reasonable latency timer
> > > value for all PCI devices, while in 2.5 we haven't as yet.
> > 
> > Do you mean whatever causes this message (for a 3com NIC)?
> > 
> > PCI: Setting latency timer of device 00:05.0 to 64
> > 
> > Would that also explain why my hard disks are slow under 2.5?  There
> > is no corresponding message for the ide controller (htp374).
> 
> I just checked the troublesome board.  Here's what lspci has to say:
> 
> 00:06.0 Display controller: 3DLabs GLINT R3 (rev 01)
> 	Subsystem: 3DLabs: Unknown device 0121
> 	Flags: bus master, 66Mhz, medium devsel, latency 0, IRQ 27
> 	Memory at 0000000009020000 (32-bit, non-prefetchable) [size=128K]
> 	Memory at 000000000c000000 (32-bit, prefetchable) [size=64M]
> 	Memory at 0000000010000000 (32-bit, prefetchable) [size=64M]
> 	Expansion ROM at 0000000009060000 [disabled] [size=64K]
> 	Capabilities: <available only to root>
> 
> The latency 0 doesn't look too good.  What should I do to change it?

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?

-- 
Måns Rullgård
mru@users.sf.net

  reply	other threads:[~2003-04-16  9:19 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 [this message]
2003-04-16 10:01                 ` Ivan Kokshaysky
2003-04-16 10:11                   ` Måns Rullgård
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=yw1x65peeqm4.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®