All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH 2/2] dma: Add IOMMU static calls with clear default ops
Date: Sat, 13 Jul 2024 12:32:59 +0300	[thread overview]
Message-ID: <20240713093259.GH1815706@unreal> (raw)
In-Reply-To: <20240713051813.GA25733@lst.de>

On Sat, Jul 13, 2024 at 07:18:13AM +0200, Christoph Hellwig wrote:
> On Fri, Jul 12, 2024 at 03:21:55PM +0100, Robin Murphy wrote:
> >> This is done to keep layering similar to existing in DMA subsystem. We
> >> have special files and calls to dma-direct, it looks natural to have
> >> special files and call to dma-iommu. It is not nice to call to drivers/iommu
> >> from kernel/dma/mapping.c
> >
> > That's where I firmly disagree. In the DMA API aspect, iommu-dma is exactly 
> > a peer of dma-direct,
> 
> Exactly.
> 
> > however it lives in drivers/iommu for practical 
> > reasons because it's more closely coupled to IOMMU API internals in all 
> > other aspects of its implementation.
> 
> TBH I think kernel/dma/ would be the better place.  But that's really the
> least my concernes at the moment.
> 
> But the important point is that I would really prefer to avoid another
> magic layer - just do direct calls like for dma-direct to keep it
> understandable (and probably faster).

I'll change my patch to be without extra layer, but is it unlikely that
it will make any difference in performance.

Thanks

> 

  reply	other threads:[~2024-07-13  9:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 10:38 [PATCH 1/2] dma: call unconditionally to unmap_page and unmap_sg callbacks Leon Romanovsky
2024-07-11 10:38 ` [PATCH 2/2] dma: Add IOMMU static calls with clear default ops Leon Romanovsky
2024-07-11 17:27   ` Leon Romanovsky
2024-07-11 18:17   ` Easwar Hariharan
2024-07-11 18:45     ` Leon Romanovsky
2024-07-11 18:23   ` Robin Murphy
2024-07-11 18:57     ` Leon Romanovsky
2024-07-11 20:08       ` Robin Murphy
2024-07-12  5:50         ` Leon Romanovsky
2024-07-12 14:21           ` Robin Murphy
2024-07-13  5:18             ` Christoph Hellwig
2024-07-13  9:32               ` Leon Romanovsky [this message]
2024-07-12  4:49     ` Christoph Hellwig
2024-07-12  6:02       ` Leon Romanovsky
2024-07-12 20:51   ` Easwar Hariharan
2024-07-13  9:30     ` Leon Romanovsky
2024-07-11 18:02 ` [PATCH 1/2] dma: call unconditionally to unmap_page and unmap_sg callbacks Robin Murphy
2024-07-12  5:47   ` Leon Romanovsky

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=20240713093259.GH1815706@unreal \
    --to=leon@kernel.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.