From: Christoph Hellwig <hch@lst.de> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Christoph Hellwig <hch@lst.de>, Greg Ungerer <gerg@linux-m68k.org>, linux-m68k <linux-m68k@lists.linux-m68k.org>, Linux IOMMU <iommu@lists.linux-foundation.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [RFC] switch m68k to use the generic remapping DMA allocator Date: Tue, 25 Jun 2019 08:32:28 +0200 [thread overview] Message-ID: <20190625063228.GA29561@lst.de> (raw) In-Reply-To: <CAMuHMdVPU5RQyX4FnHFEhxXZeG3v0uh_-t2FB=vAzQ8_3u-gSw@mail.gmail.com> On Mon, Jun 17, 2019 at 08:53:55PM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Fri, Jun 14, 2019 at 12:21 PM Christoph Hellwig <hch@lst.de> wrote: > > can you take a look at the (untested) patches below? They convert m68k > > to use the generic remapping DMA allocator, which is also used by > > arm64 and csky. > > Thanks. But what does this buy us? A common dma mapping code base with everyone, including supporting DMA allocations from atomic context, which the documentation and API assume are there, but which don't work on m68k. > bloat-o-meter says: > > add/remove: 75/0 grow/shrink: 11/6 up/down: 4122/-82 (4040) What do these values stand for? The code should grow a little as we now need to include the the pool allocator for the above API fix.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-m68k <linux-m68k@lists.linux-m68k.org>, Christoph Hellwig <hch@lst.de>, Linux IOMMU <iommu@lists.linux-foundation.org>, Greg Ungerer <gerg@linux-m68k.org> Subject: Re: [RFC] switch m68k to use the generic remapping DMA allocator Date: Tue, 25 Jun 2019 08:32:28 +0200 [thread overview] Message-ID: <20190625063228.GA29561@lst.de> (raw) In-Reply-To: <CAMuHMdVPU5RQyX4FnHFEhxXZeG3v0uh_-t2FB=vAzQ8_3u-gSw@mail.gmail.com> On Mon, Jun 17, 2019 at 08:53:55PM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Fri, Jun 14, 2019 at 12:21 PM Christoph Hellwig <hch@lst.de> wrote: > > can you take a look at the (untested) patches below? They convert m68k > > to use the generic remapping DMA allocator, which is also used by > > arm64 and csky. > > Thanks. But what does this buy us? A common dma mapping code base with everyone, including supporting DMA allocations from atomic context, which the documentation and API assume are there, but which don't work on m68k. > bloat-o-meter says: > > add/remove: 75/0 grow/shrink: 11/6 up/down: 4122/-82 (4040) What do these values stand for? The code should grow a little as we now need to include the the pool allocator for the above API fix. _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-06-25 6:33 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-14 10:21 [RFC] switch m68k to use the generic remapping DMA allocator Christoph Hellwig 2019-06-14 10:21 ` Christoph Hellwig 2019-06-14 10:21 ` [PATCH 1/2] m68k: use the generic dma coherent remap allocator Christoph Hellwig 2019-06-14 10:21 ` Christoph Hellwig 2019-06-14 10:21 ` [PATCH 2/2] m68k: implement arch_dma_prep_coherent Christoph Hellwig 2019-06-14 10:21 ` Christoph Hellwig 2019-06-17 13:39 ` [RFC] switch m68k to use the generic remapping DMA allocator Greg Ungerer 2019-06-17 13:39 ` Greg Ungerer 2019-06-17 18:53 ` Geert Uytterhoeven 2019-06-17 18:53 ` Geert Uytterhoeven 2019-06-25 6:32 ` Christoph Hellwig [this message] 2019-06-25 6:32 ` Christoph Hellwig 2019-06-25 7:26 ` Geert Uytterhoeven 2019-06-25 7:26 ` Geert Uytterhoeven 2019-06-25 7:35 ` Christoph Hellwig 2019-06-25 7:35 ` Christoph Hellwig 2019-06-25 8:07 ` Geert Uytterhoeven 2019-06-25 8:07 ` Geert Uytterhoeven 2019-06-24 7:16 ` Geert Uytterhoeven 2019-06-24 7:16 ` Geert Uytterhoeven 2019-06-25 6:33 ` Christoph Hellwig 2019-06-25 6:33 ` Christoph Hellwig
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=20190625063228.GA29561@lst.de \ --to=hch@lst.de \ --cc=geert@linux-m68k.org \ --cc=gerg@linux-m68k.org \ --cc=iommu@lists.linux-foundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-m68k@lists.linux-m68k.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: linkBe 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.