public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: arjanv@redhat.com
Cc: Jes Sorensen <jes@wildopensource.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	"David S. Miller" <davem@redhat.com>,
	Grant Grundler <grundler@dsl2.external.hp.com>,
	Colin Ngam <cngam@sgi.com>, Jeremy Higdon <jeremy@sgi.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-ia64@linuxia64.org, wildos@sgi.com
Subject: Re: [patch] support 64 bit pci_alloc_consistent
Date: 18 May 2003 09:17:48 -0500	[thread overview]
Message-ID: <1053267471.10811.28.camel@mulgrave> (raw)
In-Reply-To: <1053250142.1300.8.camel@laptop.fenrus.com>

On Sun, 2003-05-18 at 04:29, Arjan van de Ven wrote:
> An interface like
> 
> #define PCI_DMA_64BIT 0xffffffffffffffffULL
> #define PCI_DMA_32BIT 0xffffffffULL

This we can add now.

> void pci_set_dma_capabilities(device, 
>                u64 streaming_mask, u64 persistent_mask);
> u64 pci_get_effective_streaming_mask(device);
> u64 pci_get_effective_persistent_mask(device);
> 

I see the value in this for weird mask devices, but I don't think it's a
"must fix" for 2.6 since the weird mask devices can advertise a lower
standard supported mask.

The aic driver, for instance, seems to have a 39 bit addressing range
(it uses 32 bit addr and 32 bit len descriptors, but reduces len to 24
bits to steal the extra byte for 7 bits extra addressing).  However, it
is forced to request the full 64 bit address mask---I've never worked
out what will happen to it on a machine with more than 512GB memory.

The lack of a coherent_mask is causing breakage on some platforms, so
putting it in is a 2.6 must fix thing.

James


  parent reply	other threads:[~2003-05-18 14:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18  4:09 [patch] support 64 bit pci_alloc_consistent Jes Sorensen
2003-05-18  5:46 ` David S. Miller
2003-05-18  6:00 ` Andre Hedrick
2003-05-18  9:29 ` Arjan van de Ven
2003-05-18  9:35   ` David S. Miller
2003-05-18  9:43     ` Arjan van de Ven
2003-05-18 17:22       ` [Linux-ia64] " Grant Grundler
2003-05-18 17:49         ` James Bottomley
2003-05-18 20:17           ` Grant Grundler
2003-05-18 21:26             ` James Bottomley
2003-05-19 16:26               ` Grant Grundler
2003-05-18 14:17   ` James Bottomley [this message]
2003-05-18 14:21     ` Arjan van de Ven
2003-05-18 14:28       ` James Bottomley
     [not found] <mailman.1053231184.22467.linux-kernel2news@redhat.com>
2003-05-18  7:05 ` Pete Zaitcev

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=1053267471.10811.28.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=arjanv@redhat.com \
    --cc=cngam@sgi.com \
    --cc=davem@redhat.com \
    --cc=grundler@dsl2.external.hp.com \
    --cc=jeremy@sgi.com \
    --cc=jes@wildopensource.com \
    --cc=linux-ia64@linuxia64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=wildos@sgi.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