From: Jes Sorensen <jes@wildopensource.com>
To: davidm@hpl.hp.com
Cc: arjanv@redhat.com, Jeff Garzik <jgarzik@pobox.com>,
Terence Ripperda <tripperda@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 32-bit dma allocations on 64-bit platforms
Date: 30 Jun 2004 04:00:00 -0400 [thread overview]
Message-ID: <yq07jtp4gsf.fsf@wildopensource.com> (raw)
In-Reply-To: <16609.2168.754171.270072@napali.hpl.hp.com>
>>>>> "David" == David Mosberger <davidm@napali.hpl.hp.com> writes:
>>>>> On Sat, 26 Jun 2004 09:16:27 +0200, Arjan van de Ven <arjanv@redhat.com> said:
Arjan> the real solution is an iommu of course, but the highmem
Arjan> solution has quite some merit too..... I know you disagree with
Arjan> me on that one though.
David> Yes, some merits and some faults. The real solution is iommu
David> or 64-bit capable devices. Interesting that graphics
David> controllers should be last to get 64-bit DMA capability,
David> considering how much more complex they are than disk
David> controllers or NICs.
You found a 64 bit capable sound card yet? ;-)
Cheers,
Jes
next prev parent reply other threads:[~2004-06-30 8:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 18:35 32-bit dma allocations on 64-bit platforms Terence Ripperda
2004-06-23 19:19 ` Jeff Garzik
2004-06-26 5:05 ` David Mosberger
2004-06-26 7:16 ` Arjan van de Ven
2004-06-29 6:13 ` David Mosberger
2004-06-29 6:55 ` Arjan van de Ven
2004-06-30 8:00 ` Jes Sorensen [this message]
2004-06-26 5:02 ` David Mosberger
[not found] <2akPm-16l-65@gated-at.bofh.it>
2004-06-23 21:46 ` Andi Kleen
2004-06-24 6:18 ` Arjan van de Ven
2004-06-24 10:33 ` Andi Kleen
2004-06-24 13:48 ` Jesse Barnes
2004-06-24 14:39 ` Terence Ripperda
[not found] <m3acyu6pwd.fsf@averell.firstfloor.org>
[not found] ` <20040623213643.GB32456@hygelac>
2004-06-23 23:46 ` Andi Kleen
2004-06-24 11:13 ` Takashi Iwai
2004-06-24 14:45 ` Terence Ripperda
2004-06-24 15:41 ` Andrea Arcangeli
2004-06-24 15:44 ` Terence Ripperda
2004-06-24 18:51 ` Andi Kleen
2004-06-26 4:58 ` David Mosberger
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=yq07jtp4gsf.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=arjanv@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tripperda@nvidia.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 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.