linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: davem@redhat.com, linux-mm@kvack.org
Subject: Re: IOMMU setup vs DAC (PCI)
Date: Fri, 9 Feb 2001 11:47:20 -0800 (PST)	[thread overview]
Message-ID: <200102091947.LAA66193@google.engr.sgi.com> (raw)
In-Reply-To: <200102091939.LAA08207@milano.cup.hp.com> from "Grant Grundler" at Feb 09, 2001 11:39:56 AM

> 
> My original quest was for an architecturally neutral way to pass
> 64-bit physical memory addresses back to a 64-bit capable card.
> 
> pci_dma_supported() interface provides the right hook for the
> driver to advertise device capabilities. dma_addr_t is defined
> in most arches (read x86) to be 32-bit. But IA64 (u64) and mips*
> (unsigned long) have broken ground here already. I'll explore
> further to see if parisc*-linux can in fact use "unsigned long".
> 
> But I'm still interested in any comments or insights.
> (ie am I out to lunch? ;^)

dma_addr_t should be unsigned long, which is 64 bits on 64 bit
architectures, so things are fine there.

On regular x86, dma_addr_t is u32, which still works.

The problem is really on x86 PAE. I think Alan also pointed out
that other architectures might have similar issues (ARM?). For
x86-PAE, dma_addr_t should really be u64/unsigned long long. The
only issue is that there are gcc bugs while dealing with 64 bit
quantities on x86, and performance implications.

Additionally, we have also talked in the past of making a typedef
for representing physical addresses. This typedef would be the 
same as the one to represent dma_addr_t.

Kanoj

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  parent reply	other threads:[~2001-02-09 19:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09 19:39 Grant Grundler
2001-02-09 19:42 ` David S. Miller
2001-02-09 20:04   ` Grant Grundler
2001-02-09 19:47 ` Kanoj Sarcar [this message]
2001-02-09 19:52   ` David S. Miller
2001-02-09 20:07     ` Kanoj Sarcar
2001-02-09 20:23       ` David S. Miller
2001-02-09 21:11         ` Kanoj Sarcar

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=200102091947.LAA66193@google.engr.sgi.com \
    --to=kanoj@google.engr.sgi.com \
    --cc=davem@redhat.com \
    --cc=grundler@cup.hp.com \
    --cc=linux-mm@kvack.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