From: Jens Axboe <axboe@suse.de>
To: Ben LaHaise <bcrl@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>,
Jes Sorensen <jes@sunsite.dk>,
"MEHTA,HIREN (A-SanJose,ex1)" <hiren_mehta@agilent.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne
Date: Mon, 2 Jul 2001 10:09:36 +0200 [thread overview]
Message-ID: <20010702100936.C600@suse.de> (raw)
In-Reply-To: <15163.43319.82354.562310@pizda.ninka.net> <Pine.LNX.4.33.0106281823000.32276-100000@toomuch.toronto.redhat.com>
In-Reply-To: <Pine.LNX.4.33.0106281823000.32276-100000@toomuch.toronto.redhat.com>
On Thu, Jun 28 2001, Ben LaHaise wrote:
> On Thu, 28 Jun 2001, David S. Miller wrote:
>
> > Please note that this is nonstandard and undocumented behavior.
> >
> > This is not a supported API at all, and the way 64-bit DMA will
> > eventually be done across all platforms is likely to be different.
>
> Well, what is the standard API to use? All these 64 bit cards in my
> machine really make that 95% cpu usage in bounce buffer copying rather
> depressing.
The current sg list and single mapping functions are useless on 64-bit
(and highmem) anyway. I've used struct sg_list as a scatterlist
replacement for some time that holds a page/offset/length thing instead,
and also used pci_map_page for single mappings.
Using a virtual address for this stuff seems a bit short-sighted to
me...
--
Jens Axboe
next prev parent reply other threads:[~2001-07-02 8:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 16:20 (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne MEHTA,HIREN (A-SanJose,ex1)
2001-06-28 19:41 ` Jes Sorensen
2001-06-28 22:01 ` David S. Miller
2001-06-28 22:20 ` Jes Sorensen
2001-06-28 22:27 ` David S. Miller
2001-06-28 22:28 ` Alan Cox
2001-07-02 8:09 ` Jens Axboe
2001-06-28 22:24 ` Ben LaHaise
2001-06-28 22:29 ` David S. Miller
2001-06-28 22:31 ` Ben LaHaise
2001-06-28 22:38 ` David S. Miller
2001-06-28 22:45 ` Ben LaHaise
2001-06-28 22:48 ` David S. Miller
2001-06-28 22:48 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-06-28 22:55 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne Jes Sorensen
2001-06-29 9:16 ` David S. Miller
2001-06-29 9:56 ` Alan Cox
2001-06-29 20:37 ` David S. Miller
2001-07-05 21:06 ` Jes Sorensen
2001-07-05 23:47 ` David S. Miller
2001-07-05 23:50 ` Ben LaHaise
2001-07-06 13:31 ` Jes Sorensen
2001-07-06 23:46 ` David S. Miller
2001-07-07 3:58 ` Ben LaHaise
2001-07-07 5:35 ` David S. Miller
2001-07-07 12:06 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-07-07 12:17 ` Jeff Garzik
2001-07-07 12:21 ` Alan Cox
2001-07-07 13:00 ` David S. Miller
2001-07-11 19:16 ` Jes Sorensen
2001-07-11 21:54 ` Chris Wedgwood
2001-07-11 23:17 ` David S. Miller
2001-07-11 23:07 ` David S. Miller
2001-06-28 22:40 ` Alan Cox
2001-07-02 8:09 ` Jens Axboe [this message]
2001-06-28 21:45 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne David S. Miller
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=20010702100936.C600@suse.de \
--to=axboe@suse.de \
--cc=bcrl@redhat.com \
--cc=davem@redhat.com \
--cc=hiren_mehta@agilent.com \
--cc=jes@sunsite.dk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox