From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: libata+SGIO: is .dma_boundary respected? Date: Tue, 21 Mar 2006 14:31:16 -0500 Message-ID: <44205484.9000702@rtr.ca> References: <441DC397.9040504@rtr.ca> <441DC9CB.7030203@pobox.com> <441DCAC9.5090603@rtr.ca> <441DCF73.2080600@pobox.com> <441DD101.5050202@rtr.ca> <441DD300.9050702@rtr.ca> <441F544A.6080301@pobox.com> <441F8478.50806@rtr.ca> <441F99AC.4000200@pobox.com> <442006BC.8020100@rtr.ca> <20060321184215.GJ4285@suse.de> <442051A0.1050200@rtr.ca> <4420541E.3070303@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from rtr.ca ([64.26.128.89]:1980 "EHLO mail.rtr.ca") by vger.kernel.org with ESMTP id S932349AbWCUTbU (ORCPT ); Tue, 21 Mar 2006 14:31:20 -0500 In-Reply-To: <4420541E.3070303@pobox.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Jeff Garzik Cc: Jens Axboe , IDE/ATA development list , James Bottomley , Benjamin Herrenschmidt Jeff Garzik wrote: > >> In the case of sata_mv on the Marvell 6081 (which I'm looking at this >> week) >> it's hardware limit is actually 0xffffffff rather than 0xffff. > > If the limit is not 0xffff, then there's no need for any of this > limitation junk. No s/g entry splitting after pci_map_sg(), no > artificial sg_tablesize limitation, etc. Not even for a merged IOMMU segment that crosses the 4GB "boundary" ?