From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Ravnborg Date: Wed, 07 Jan 2009 19:56:46 +0000 Subject: Re: [PATCH 0/13] IA64: unifying ways to handle multiple sets of dma mapping ops Message-Id: <20090107195646.GE4647@uranus.ravnborg.org> List-Id: References: <1231166178-20050-1-git-send-email-fujita.tomonori@lab.ntt.co.jp> In-Reply-To: <1231166178-20050-1-git-send-email-fujita.tomonori@lab.ntt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: FUJITA Tomonori Cc: tony.luck@intel.com, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" On Mon, Jan 05, 2009 at 11:36:05PM +0900, FUJITA Tomonori wrote: > This patchset is the first part of the unification of ways to handle > multiple sets of dma mapping API. The whole work consists of three > patchset. This is for IA64 and can be applied independently. > > dma_mapping_ops (or dma_ops) struct is used to handle multiple sets of > dma mapping API by X86, SPARC, and POWER. IA64 also handle multiple > sets of dma mapping API but in a very different way (some define > magic). > > X86 and IA64 share VT-d and SWIOTLB code. We need several workarounds > for it because of the deference of ways to handle multiple sets of dma > mapping API (e.g., X86 people can't freely change struct > dma_mapping_ops in x86's dma-mapping.h now because it could break > IA64). Seems POWER will use SWIOTLB code soon. I think that it's time > to unify ways to handle multiple sets of dma mapping API. After > applying the whole work, we have struct dma_map_ops > include/linux/dma-mapping.h (I also dream of changing all the archs to > use SWIOTLB in order to remove the bounce code in the block and > network stacks...). > > This patchset changes IA64 to handle multiple sets of dma mapping API > in the common way (as X86, SPARC, and POWER do): Do you have any plans to update sparc too? Maybe it is not relevant. Sam