From: Christoph Hellwig <hch@lst.de>
To: Tomasz Figa <tfiga@chromium.org>
Cc: Christoph Hellwig <hch@lst.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Ben Skeggs <bskeggs@redhat.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Matt Porter <mporter@kernel.crashing.org>,
iommu@lists.linux-foundation.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-devel@lists.sourceforge.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
nouveau@lists.freedesktop.org, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-mm@kvack.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 17/18] dma-iommu: implement ->alloc_noncoherent
Date: Sat, 26 Sep 2020 16:14:28 +0200 [thread overview]
Message-ID: <20200926141428.GB10379@lst.de> (raw)
In-Reply-To: <20200925184622.GB3607091@chromium.org>
On Fri, Sep 25, 2020 at 06:46:22PM +0000, Tomasz Figa wrote:
> > +static void *iommu_dma_alloc_noncoherent(struct device *dev, size_t size,
> > + dma_addr_t *handle, enum dma_data_direction dir, gfp_t gfp)
> > +{
> > + if (!gfpflags_allow_blocking(gfp)) {
> > + struct page *page;
> > +
> > + page = dma_common_alloc_pages(dev, size, handle, dir, gfp);
> > + if (!page)
> > + return NULL;
> > + return page_address(page);
> > + }
> > +
> > + return iommu_dma_alloc_remap(dev, size, handle, gfp | __GFP_ZERO,
> > + PAGE_KERNEL, 0);
>
> iommu_dma_alloc_remap() makes use of the DMA_ATTR_ALLOC_SINGLE_PAGES attribute
> to optimize the allocations for devices which don't care about how contiguous
> the backing memory is. Do you think we could add an attrs argument to this
> function and pass it there?
>
> As ARM is being moved to the common iommu-dma layer as well, we'll probably
> make use of the argument to support the DMA_ATTR_NO_KERNEL_MAPPING attribute to
> conserve the vmalloc area.
We could probably at it. However I wonder why this is something the
drivers should care about. Isn't this really something that should
be a kernel-wide policy for a given system?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tomasz Figa <tfiga@chromium.org>
Cc: alsa-devel@alsa-project.org, linux-doc@vger.kernel.org,
nouveau@lists.freedesktop.org, linux-mips@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-mm@kvack.org, linux1394-devel@lists.sourceforge.net,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-samsung-soc@vger.kernel.org,
Joonyoung Shim <jy0922.shim@samsung.com>,
linux-scsi@vger.kernel.org, Ben Skeggs <bskeggs@redhat.com>,
Matt Porter <mporter@kernel.crashing.org>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-parisc@vger.kernel.org, netdev@vger.kernel.org,
Seung-Woo Kim <sw0312.kim@samsung.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH 17/18] dma-iommu: implement ->alloc_noncoherent
Date: Sat, 26 Sep 2020 16:14:28 +0200 [thread overview]
Message-ID: <20200926141428.GB10379@lst.de> (raw)
In-Reply-To: <20200925184622.GB3607091@chromium.org>
On Fri, Sep 25, 2020 at 06:46:22PM +0000, Tomasz Figa wrote:
> > +static void *iommu_dma_alloc_noncoherent(struct device *dev, size_t size,
> > + dma_addr_t *handle, enum dma_data_direction dir, gfp_t gfp)
> > +{
> > + if (!gfpflags_allow_blocking(gfp)) {
> > + struct page *page;
> > +
> > + page = dma_common_alloc_pages(dev, size, handle, dir, gfp);
> > + if (!page)
> > + return NULL;
> > + return page_address(page);
> > + }
> > +
> > + return iommu_dma_alloc_remap(dev, size, handle, gfp | __GFP_ZERO,
> > + PAGE_KERNEL, 0);
>
> iommu_dma_alloc_remap() makes use of the DMA_ATTR_ALLOC_SINGLE_PAGES attribute
> to optimize the allocations for devices which don't care about how contiguous
> the backing memory is. Do you think we could add an attrs argument to this
> function and pass it there?
>
> As ARM is being moved to the common iommu-dma layer as well, we'll probably
> make use of the argument to support the DMA_ATTR_NO_KERNEL_MAPPING attribute to
> conserve the vmalloc area.
We could probably at it. However I wonder why this is something the
drivers should care about. Isn't this really something that should
be a kernel-wide policy for a given system?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tomasz Figa <tfiga@chromium.org>
Cc: Christoph Hellwig <hch@lst.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Ben Skeggs <bskeggs@redhat.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Matt Porter <mporter@kernel.crashing.org>,
iommu@lists.linux-foundation.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-devel@lists.sourceforge.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
nouveau@lists.freedesktop.org, netdev@vger.kernel.
Subject: Re: [PATCH 17/18] dma-iommu: implement ->alloc_noncoherent
Date: Sat, 26 Sep 2020 16:14:28 +0200 [thread overview]
Message-ID: <20200926141428.GB10379@lst.de> (raw)
In-Reply-To: <20200925184622.GB3607091@chromium.org>
On Fri, Sep 25, 2020 at 06:46:22PM +0000, Tomasz Figa wrote:
> > +static void *iommu_dma_alloc_noncoherent(struct device *dev, size_t size,
> > + dma_addr_t *handle, enum dma_data_direction dir, gfp_t gfp)
> > +{
> > + if (!gfpflags_allow_blocking(gfp)) {
> > + struct page *page;
> > +
> > + page = dma_common_alloc_pages(dev, size, handle, dir, gfp);
> > + if (!page)
> > + return NULL;
> > + return page_address(page);
> > + }
> > +
> > + return iommu_dma_alloc_remap(dev, size, handle, gfp | __GFP_ZERO,
> > + PAGE_KERNEL, 0);
>
> iommu_dma_alloc_remap() makes use of the DMA_ATTR_ALLOC_SINGLE_PAGES attribute
> to optimize the allocations for devices which don't care about how contiguous
> the backing memory is. Do you think we could add an attrs argument to this
> function and pass it there?
>
> As ARM is being moved to the common iommu-dma layer as well, we'll probably
> make use of the argument to support the DMA_ATTR_NO_KERNEL_MAPPING attribute to
> conserve the vmalloc area.
We could probably at it. However I wonder why this is something the
drivers should care about. Isn't this really something that should
be a kernel-wide policy for a given system?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tomasz Figa <tfiga@chromium.org>
Cc: alsa-devel@alsa-project.org, linux-doc@vger.kernel.org,
nouveau@lists.freedesktop.org, linux-mips@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-mm@kvack.org, linux1394-devel@lists.sourceforge.net,
Christoph Hellwig <hch@lst.de>,
linux-samsung-soc@vger.kernel.org,
Joonyoung Shim <jy0922.shim@samsung.com>,
linux-scsi@vger.kernel.org, Ben Skeggs <bskeggs@redhat.com>,
Matt Porter <mporter@kernel.crashing.org>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-parisc@vger.kernel.org, netdev@vger.kernel.org,
Seung-Woo Kim <sw0312.kim@samsung.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH 17/18] dma-iommu: implement ->alloc_noncoherent
Date: Sat, 26 Sep 2020 16:14:28 +0200 [thread overview]
Message-ID: <20200926141428.GB10379@lst.de> (raw)
In-Reply-To: <20200925184622.GB3607091@chromium.org>
On Fri, Sep 25, 2020 at 06:46:22PM +0000, Tomasz Figa wrote:
> > +static void *iommu_dma_alloc_noncoherent(struct device *dev, size_t size,
> > + dma_addr_t *handle, enum dma_data_direction dir, gfp_t gfp)
> > +{
> > + if (!gfpflags_allow_blocking(gfp)) {
> > + struct page *page;
> > +
> > + page = dma_common_alloc_pages(dev, size, handle, dir, gfp);
> > + if (!page)
> > + return NULL;
> > + return page_address(page);
> > + }
> > +
> > + return iommu_dma_alloc_remap(dev, size, handle, gfp | __GFP_ZERO,
> > + PAGE_KERNEL, 0);
>
> iommu_dma_alloc_remap() makes use of the DMA_ATTR_ALLOC_SINGLE_PAGES attribute
> to optimize the allocations for devices which don't care about how contiguous
> the backing memory is. Do you think we could add an attrs argument to this
> function and pass it there?
>
> As ARM is being moved to the common iommu-dma layer as well, we'll probably
> make use of the argument to support the DMA_ATTR_NO_KERNEL_MAPPING attribute to
> conserve the vmalloc area.
We could probably at it. However I wonder why this is something the
drivers should care about. Isn't this really something that should
be a kernel-wide policy for a given system?
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tomasz Figa <tfiga@chromium.org>
Cc: alsa-devel@alsa-project.org, linux-doc@vger.kernel.org,
nouveau@lists.freedesktop.org, linux-mips@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-mm@kvack.org, linux1394-devel@lists.sourceforge.net,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-samsung-soc@vger.kernel.org,
Joonyoung Shim <jy0922.shim@samsung.com>,
linux-scsi@vger.kernel.org, Ben Skeggs <bskeggs@redhat.com>,
Matt Porter <mporter@kernel.crashing.org>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-parisc@vger.kernel.org, netdev@vger.kernel.org,
Seung-Woo Kim <sw0312.kim@samsung.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH 17/18] dma-iommu: implement ->alloc_noncoherent
Date: Sat, 26 Sep 2020 16:14:28 +0200 [thread overview]
Message-ID: <20200926141428.GB10379@lst.de> (raw)
In-Reply-To: <20200925184622.GB3607091@chromium.org>
On Fri, Sep 25, 2020 at 06:46:22PM +0000, Tomasz Figa wrote:
> > +static void *iommu_dma_alloc_noncoherent(struct device *dev, size_t size,
> > + dma_addr_t *handle, enum dma_data_direction dir, gfp_t gfp)
> > +{
> > + if (!gfpflags_allow_blocking(gfp)) {
> > + struct page *page;
> > +
> > + page = dma_common_alloc_pages(dev, size, handle, dir, gfp);
> > + if (!page)
> > + return NULL;
> > + return page_address(page);
> > + }
> > +
> > + return iommu_dma_alloc_remap(dev, size, handle, gfp | __GFP_ZERO,
> > + PAGE_KERNEL, 0);
>
> iommu_dma_alloc_remap() makes use of the DMA_ATTR_ALLOC_SINGLE_PAGES attribute
> to optimize the allocations for devices which don't care about how contiguous
> the backing memory is. Do you think we could add an attrs argument to this
> function and pass it there?
>
> As ARM is being moved to the common iommu-dma layer as well, we'll probably
> make use of the argument to support the DMA_ATTR_NO_KERNEL_MAPPING attribute to
> conserve the vmalloc area.
We could probably at it. However I wonder why this is something the
drivers should care about. Isn't this really something that should
be a kernel-wide policy for a given system?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-26 14:14 UTC|newest]
Thread overview: 176+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 15:51 a saner API for allocating DMA addressable pages v3 Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` [PATCH 01/18] media/v4l2: remove V4L2-FLAG-MEMORY-NON-CONSISTENT flag Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-25 18:47 ` Tomasz Figa
2020-09-25 18:47 ` Tomasz Figa
2020-09-25 18:47 ` Tomasz Figa
2020-09-25 18:47 ` Tomasz Figa
2020-09-25 18:47 ` Tomasz Figa
2020-09-15 15:51 ` [PATCH 02/18] mm: turn alloc_pages into an inline function Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` [PATCH 03/18] drm/exynos: stop setting DMA_ATTR_NON_CONSISTENT Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` [PATCH 04/18] drm/nouveau/gk20a: " Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` [PATCH 05/18] net/au1000-eth: stop using DMA_ATTR_NON_CONSISTENT Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` [PATCH 06/18] lib82596: move DMA allocation into the callers of i82596_probe Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:48 ` Thomas Bogendoerfer
2020-09-22 8:48 ` Thomas Bogendoerfer
2020-09-22 8:48 ` Thomas Bogendoerfer
2020-09-22 8:48 ` Thomas Bogendoerfer
2020-09-22 8:48 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 07/18] 53c700: improve non-coherent DMA handling Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 08/18] dma-mapping: add a new dma_alloc_noncoherent API Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-25 11:15 ` Robin Murphy
2020-09-25 11:15 ` Robin Murphy
2020-09-25 11:15 ` Robin Murphy
2020-09-25 16:17 ` Christoph Hellwig
2020-09-25 16:17 ` Christoph Hellwig
2020-09-25 16:17 ` Christoph Hellwig
2020-09-25 16:17 ` Christoph Hellwig
2020-09-25 16:17 ` Christoph Hellwig
2020-09-15 15:51 ` [PATCH 09/18] sgiwd93: convert to dma_alloc_noncoherent Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-22 8:49 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 10/18] hal2: " Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 11/18] lib82596: " Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-22 8:50 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 12/18] sgiseeq: " Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 13/18] 53c700: " Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-22 8:51 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 14/18] dma-mapping: remove dma_cache_sync Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:52 ` Thomas Bogendoerfer
2020-09-22 8:52 ` Thomas Bogendoerfer
2020-09-22 8:52 ` Thomas Bogendoerfer
2020-09-22 8:52 ` Thomas Bogendoerfer
2020-09-22 8:52 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 15/18] dma-mapping: add a new dma_alloc_pages API Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-22 8:53 ` Thomas Bogendoerfer
2020-09-22 8:53 ` Thomas Bogendoerfer
2020-09-22 8:53 ` Thomas Bogendoerfer
2020-09-22 8:53 ` Thomas Bogendoerfer
2020-09-22 8:53 ` Thomas Bogendoerfer
2020-09-15 15:51 ` [PATCH 16/18] dma-mapping: add new {alloc,free}_noncoherent dma_map_ops methods Christoph Hellwig
2020-09-15 15:51 ` [PATCH 16/18] dma-mapping: add new {alloc, free}_noncoherent " Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` [PATCH 17/18] dma-iommu: implement ->alloc_noncoherent Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-25 18:46 ` Tomasz Figa
2020-09-25 18:46 ` Tomasz Figa
2020-09-25 18:46 ` Tomasz Figa
2020-09-25 18:46 ` Tomasz Figa
2020-09-25 18:46 ` Tomasz Figa
2020-09-26 14:14 ` Christoph Hellwig [this message]
2020-09-26 14:14 ` Christoph Hellwig
2020-09-26 14:14 ` Christoph Hellwig
2020-09-26 14:14 ` Christoph Hellwig
2020-09-26 14:14 ` Christoph Hellwig
2020-09-26 15:25 ` Tomasz Figa
2020-09-26 15:25 ` Tomasz Figa
2020-09-26 15:25 ` Tomasz Figa
2020-09-26 15:25 ` Tomasz Figa
2020-09-26 15:25 ` Tomasz Figa
2020-09-26 15:25 ` Tomasz Figa
2020-09-15 15:51 ` [PATCH 18/18] firewire-ohci: use dma_alloc_pages Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-15 15:51 ` Christoph Hellwig
2020-09-21 6:36 ` a saner API for allocating DMA addressable pages v3 Christoph Hellwig
2020-09-21 6:36 ` Christoph Hellwig
2020-09-21 6:36 ` Christoph Hellwig
2020-09-21 6:36 ` Christoph Hellwig
2020-09-25 4:21 ` Christoph Hellwig
2020-09-25 4:21 ` Christoph Hellwig
2020-09-25 4:21 ` 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=20200926141428.GB10379@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alsa-devel@alsa-project.org \
--cc=bskeggs@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jy0922.shim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=mporter@kernel.crashing.org \
--cc=netdev@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=sw0312.kim@samsung.com \
--cc=tfiga@chromium.org \
--cc=tsbogend@alpha.franken.de \
/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.