Re: [patch] zero-bounce highmem I/O

From: Jens Axboe <axboe@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, andrea@suse.de
Subject: Re: [patch] zero-bounce highmem I/O
Date: Wed, 15 Aug 2001 14:07:40 +0200	[thread overview]
Message-ID: <20010815140740.A4352@suse.de> (raw)
In-Reply-To: <20010815112621.F545@suse.de> <20010815.032218.55508716.davem@redhat.com> <20010815131335.H545@suse.de> <20010815.044757.112624116.davem@redhat.com>
In-Reply-To: <20010815.044757.112624116.davem@redhat.com>

On Wed, Aug 15 2001, David S. Miller wrote:
>    From: Jens Axboe <axboe@suse.de>
>    Date: Wed, 15 Aug 2001 13:13:35 +0200
> 
>    Looks fine to me, exactly the interface I've used/wanted. But you want
>    to add the extra page/offset to the existing scatterlist, and not scrap
>    that one completely?
> 
> The idea is that address/alt_address disappear sometime in 2.5.
> Something like this right?

Ok so you just want to turn scatterlist into what I call sg_list in 2.5
time, fine with me too. Depends on whether we want to keep the
pci_map_sg and struct scatterlist interface intact, or just break it and
tell driver authors they must fix their stuff regardless of whether they
want to support highmem. As I write this sentence, it's clear to me
which way is the superior :-)

> BTW, on x86 we can ifdef the dma64_address to u32 or u64 based
> upon CONFIG_HIGHMEM if we wish.

Yep. Want me to add in the x86 parts of your patch?

-- 
Jens Axboe