From: mru@users.sourceforge.net (Måns Rullgård)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DMA transfers in 2.5.67
Date: 16 Apr 2003 00:09:00 +0200 [thread overview]
Message-ID: <yw1xptnne7lv.fsf@zaphod.guide> (raw)
In-Reply-To: <1050439715.28586.17.camel@dhcp22.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > It's an Alpha with 768 MB. Is it the pci_alloc_* functions you are
> > referring to? I don't think they are used currently. How much memory
> > can these allocate? I need chunks of up to 1 MB, not necessarily
> > phycically continuous.
> >
> > What do those functions do that normal memory allocation does not?
> > Apart from setting up sg mappings, that is.
>
> A normal memory allocation might not be visible from the device, however
> pci_map_sg() deals with such things. What I really meant was are you
> using the pci_ DMA functionality
Those functions are not used at the moment, but I could change that.
The question remains why DMA transfers are so slow. The memory is
clearly visible from the bus.
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?
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-04-15 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 20:01 DMA transfers in 2.5.67 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=yw1xptnne7lv.fsf@zaphod.guide \
--to=mru@users.sourceforge.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.