All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [patch] support 64 bit pci_alloc_consistent
Date: Sun, 18 May 2003 14:21:30 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705934@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705928@msgid-missing>

On Sun, May 18, 2003 at 09:17:48AM -0500, James Bottomley wrote:
> (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.

Uh??? right now even in 2.4 arbitrary bitmasks are supported for
non-coherent memory.


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18  5:46 [Linux-ia64] Re: [patch] support 64 bit pci_alloc_consistent 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 14:17 ` James Bottomley
2003-05-18 14:21 ` Arjan van de Ven [this message]
2003-05-18 14:28 ` James Bottomley
2003-05-18 17:22 ` 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
  -- strict thread matches above, loose matches on Subject: below --
2003-05-18  4:09 Jes Sorensen
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

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=marc-linux-ia64-105590723705934@msgid-missing \
    --to=arjanv@redhat.com \
    --cc=linux-ia64@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.