linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: sam@ravnborg.org
Cc: fujita.tomonori@lab.ntt.co.jp, tony.luck@intel.com,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [PATCH 0/13] IA64: unifying ways to handle multiple sets of dma mapping ops
Date: Thu, 8 Jan 2009 10:55:04 +0900	[thread overview]
Message-ID: <20090108105518B.fujita.tomonori@lab.ntt.co.jp> (raw)
In-Reply-To: <20090107195646.GE4647@uranus.ravnborg.org>

On Wed, 7 Jan 2009 20:56:46 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:

> 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.

I'll do after finishing IA64 and X86. It's not a huge gain since SPARC
doesn't share IOMMU code with other architectures. But I think that it
would be nice to remove arch/sparc/include/asm/dma-mapping_64.h

The long-term goal is removing the bounce code in the network and
block stacks, and some drivers (using sorta SWIOTLB on non IOMMU
systems instead). So I try to convert all the architectures to use
this generic mechanism (though I'm not sure all the arch maintainers
agree with it).

Thanks,

      reply	other threads:[~2009-01-08  1:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 14:36 [PATCH 0/13] IA64: unifying ways to handle multiple sets of dma mapping ops FUJITA Tomonori
2009-01-05 14:36 ` [PATCH 01/13] add map/unmap_single_attr and map/unmap_sg_attr to struct dma_mapping_ops FUJITA Tomonori
2009-01-05 14:36   ` [PATCH 02/13] add dma_mapping_ops for SBA IOMMU FUJITA Tomonori
2009-01-05 14:36     ` [PATCH 03/13] add dma_mapping_ops for SWIOTLB and " FUJITA Tomonori
2009-01-05 14:36       ` [PATCH 04/13] add dma_mapping_ops for intel-iommu FUJITA Tomonori
2009-01-05 14:36         ` [PATCH 05/13] add dma_mapping_ops for SGI Altix FUJITA Tomonori
2009-01-05 14:36           ` [PATCH 06/13] add dma_mapping_ops for SWIOTLB FUJITA Tomonori
2009-01-05 14:36             ` [PATCH 07/13] set up dma_ops appropriately FUJITA Tomonori
2009-01-05 14:36               ` [PATCH 08/13] convert the DMA API to use dma_ops FUJITA Tomonori
2009-01-05 14:36                 ` [PATCH 09/13] remove dma operations in struct ia64_machine_vector FUJITA Tomonori
2009-01-05 14:36                   ` [PATCH 10/13] make sn DMA mapping functions static FUJITA Tomonori
2009-01-05 14:36                     ` [PATCH 11/13] add dma_get_ops to struct ia64_machine_vector FUJITA Tomonori
2009-01-05 14:36                       ` [PATCH 12/13] remove hwsw_dma_ops FUJITA Tomonori
2009-01-05 14:36                         ` [PATCH 13/13] make sba DMA mapping functions static FUJITA Tomonori
2009-01-07 19:56 ` [PATCH 0/13] IA64: unifying ways to handle multiple sets of dma mapping ops Sam Ravnborg
2009-01-08  1:55   ` FUJITA Tomonori [this message]

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=20090108105518B.fujita.tomonori@lab.ntt.co.jp \
    --to=fujita.tomonori@lab.ntt.co.jp \
    --cc=davem@davemloft.net \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tony.luck@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).