Date: Wed, 2 Jul 2003 02:22:44 +0200
From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: James.Bottomley@steeleye.com, axboe@suse.de, grundler@parisc-linux.org,
       suparna@in.ibm.com, linux-kernel@vger.kernel.org,
       alex_williamson@hp.com, bjorn_helgaas@hp.com
Subject: Re: [RFC] block layer support for DMA IOMMU bypass mode II
Message-Id: <20030702022244.030a8acc.ak@suse.de>
In-Reply-To: <20030701.170323.59686965.davem@redhat.com>
References: <1057077975.2135.54.camel@mulgrave>
	<20030702015701.6007ac26.ak@suse.de>
	<20030701.170323.59686965.davem@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1097
Lines: 25

On Tue, 01 Jul 2003 17:03:23 -0700 (PDT)
"David S. Miller" <davem@redhat.com> wrote:

>    From: Andi Kleen <ak@suse.de>
>    Date: Wed, 2 Jul 2003 01:57:01 +0200
>    
>    The K8 IOMMU cannot support this virtually contiguous thing. The reason
>    is that there is no guarantee that an entry in a sglist is a multiple
>    of page size. And the aperture can only map 4K sized chunks, like 
>    a CPU MMU. So e.g. when you have an sglist with multiple 1K entries there is 
> What do you mean?  You map only one 4K chunk, and this is used
> for all the sub-1K mappings.

How should this work when the 1K mappings are spread all over memory?

Maybe I'm missing something but from James description it sounds like the 
block layer assumes that it can pass in a sglist with arbitary elements 
and get it back remapped to continuous DMA addresses.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/