public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Evan Lavelle <sa212+lkml@cyconix.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Driver: PCIe: 'pci_map_sg' returning invalid bus address?
Date: Sun, 15 Aug 2010 21:31:29 -0600	[thread overview]
Message-ID: <4C68B111.9090302@gmail.com> (raw)
In-Reply-To: <4C66B580.5060606@cyconix.com>

On 08/14/2010 09:25 AM, Evan Lavelle wrote:
> Thanks guys. I had to get this working quickly so I just stuck with my
> bounce buffer code. I'm not sure that it's technically a 'bounce
> buffer'; it just so happens that 'pci_alloc_consistent' returns an
> address in the low 32 bits. This may stop working if the user installs
> more than 4Gig of memory but I can live with that for now. Performance

That should be safe as far as x86-32 goes - pci_alloc_consistent will 
return a low memory address which will be below 1GB.

> isn't great (~110Mbytes/s on 4-channel PCIe) but it's good enough.
>
> It's disappointing that LDD didn't have anything to say about this; it's
> pretty fundamental to DMA on x86_32 and PAE.

The situation kind of sucks with that combination, yes. The block and 
network subsystems have their own workarounds but other drivers just 
have to sort of hack something together.

      reply	other threads:[~2010-08-16  3:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 10:13 Driver: PCIe: 'pci_map_sg' returning invalid bus address? Evan Lavelle
2010-08-04  9:26 ` Evan Lavelle
2010-08-04 10:08   ` FUJITA Tomonori
2010-08-04 11:22     ` Evan Lavelle
2010-08-04 12:03       ` FUJITA Tomonori
2010-08-04 14:51         ` Konrad Rzeszutek Wilk
2010-08-13  1:35           ` Yuhong Bao
2010-08-14 15:25 ` Evan Lavelle
2010-08-16  3:31   ` Robert Hancock [this message]

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=4C68B111.9090302@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sa212+lkml@cyconix.com \
    /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