From: Jens Axboe <axboe@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: kraxel@bytesex.org, linux-kernel@vger.kernel.org
Subject: Re: struct page to 36 (or 64) bit bus address?
Date: Sat, 11 Aug 2001 17:32:20 +0200 [thread overview]
Message-ID: <20010811173220.B1721@suse.de> (raw)
In-Reply-To: <15218.61869.424038.30544@pizda.ninka.net> <20010809163531.D1575@sventech.com> <slrn9n71kn.28q.kraxel@bytesex.org> <20010810.145836.41632779.davem@redhat.com>
In-Reply-To: <20010810.145836.41632779.davem@redhat.com>
On Fri, Aug 10 2001, David S. Miller wrote:
>
> I'm using the patch below (pulled out of Jens Axboe's bio
> patches, i386 only).
>
> Are you sure you aren't missing anything in this patch? For example,
> one can't use the patch you've provided for 64-bit DMA unless the
> dma_addr_t type is made larger.
The dma_addr_high_t was dumped along with pci_map_page_high etc, on your
request in fact :-). So all that is there currently is highmem capable
32-bit DMA stuff.
--
Jens Axboe
next prev parent reply other threads:[~2001-08-11 15:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 18:40 struct page to 36 (or 64) bit bus address? Johannes Erdfelt
2001-08-09 19:09 ` Alan Cox
2001-08-09 19:10 ` Johannes Erdfelt
2001-08-09 19:19 ` Alan Cox
2001-08-09 20:25 ` David S. Miller
2001-08-09 20:35 ` Johannes Erdfelt
2001-08-10 7:00 ` Gerd Knorr
2001-08-10 7:56 ` Johannes Erdfelt
2001-08-10 21:58 ` David S. Miller
2001-08-11 7:09 ` Gerd Knorr
2001-08-12 10:49 ` Write Combining (Write Coalescing) on memory mapped I/O on IA64 Steffen Persvold
2001-08-11 15:32 ` Jens Axboe [this message]
2001-08-11 15:56 ` struct page to 36 (or 64) bit bus address? Andrea Arcangeli
2001-08-11 16:13 ` Sandy Harris
2001-08-12 8:00 ` David S. Miller
[not found] <no.id>
2001-08-12 11:49 ` Alan Cox
2001-08-13 13:51 ` David S. Miller
2001-08-13 14:09 ` Alan Cox
2001-08-13 14:21 ` David S. Miller
2001-08-13 19:07 ` Gérard Roudier
2001-08-13 19:42 ` David S. Miller
2001-08-13 15:10 ` Alan Cox
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=20010811173220.B1721@suse.de \
--to=axboe@suse.de \
--cc=davem@redhat.com \
--cc=kraxel@bytesex.org \
--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 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.