From: Christoph Hellwig <hch@lst.de>
To: "Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon.com>
Cc: "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
Linuxarm <linuxarm@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"ganapatrao.kulkarni@cavium.com" <ganapatrao.kulkarni@cavium.com>,
huangdaode <huangdaode@huawei.com>,
"will@kernel.org" <will@kernel.org>,
Christoph Hellwig <hch@lst.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 0/2] make dma_alloc_coherent NUMA-aware by per-NUMA CMA
Date: Mon, 31 Aug 2020 10:40:18 +0200 [thread overview]
Message-ID: <20200831084018.GA903@lst.de> (raw)
In-Reply-To: <05dad074e0624367a3fc0dfd0b96a352@hisilicon.com>
This is on my todo list to be applied this week.
_______________________________________________
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: "Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon.com>
Cc: "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
Linuxarm <linuxarm@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"ganapatrao.kulkarni@cavium.com" <ganapatrao.kulkarni@cavium.com>,
huangdaode <huangdaode@huawei.com>,
"will@kernel.org" <will@kernel.org>,
Christoph Hellwig <hch@lst.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>
Subject: Re: [PATCH v6 0/2] make dma_alloc_coherent NUMA-aware by per-NUMA CMA
Date: Mon, 31 Aug 2020 10:40:18 +0200 [thread overview]
Message-ID: <20200831084018.GA903@lst.de> (raw)
In-Reply-To: <05dad074e0624367a3fc0dfd0b96a352@hisilicon.com>
This is on my todo list to be applied this week.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: "Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon.com>
Cc: Christoph Hellwig <hch@lst.de>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"will@kernel.org" <will@kernel.org>,
"ganapatrao.kulkarni@cavium.com" <ganapatrao.kulkarni@cavium.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
Linuxarm <linuxarm@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
huangdaode <huangdaode@huawei.com>
Subject: Re: [PATCH v6 0/2] make dma_alloc_coherent NUMA-aware by per-NUMA CMA
Date: Mon, 31 Aug 2020 10:40:18 +0200 [thread overview]
Message-ID: <20200831084018.GA903@lst.de> (raw)
In-Reply-To: <05dad074e0624367a3fc0dfd0b96a352@hisilicon.com>
This is on my todo list to be applied this week.
next prev parent reply other threads:[~2020-08-31 8:40 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 2:26 [PATCH v6 0/2] make dma_alloc_coherent NUMA-aware by per-NUMA CMA Barry Song
2020-08-21 2:26 ` Barry Song
2020-08-21 2:26 ` Barry Song
2020-08-21 2:26 ` [PATCH v6 1/2] dma-contiguous: provide the ability to reserve per-numa CMA Barry Song
2020-08-21 2:26 ` Barry Song
2020-08-21 2:26 ` Barry Song
2020-08-21 2:49 ` Randy Dunlap
2020-08-21 2:49 ` Randy Dunlap
2020-08-21 2:49 ` Randy Dunlap
2020-08-21 8:29 ` Song Bao Hua (Barry Song)
2020-08-21 8:29 ` Song Bao Hua (Barry Song)
2020-08-21 8:29 ` Song Bao Hua (Barry Song)
2020-08-21 8:47 ` Will Deacon
2020-08-21 8:47 ` Will Deacon
2020-08-21 8:47 ` Will Deacon
2020-08-21 9:13 ` Song Bao Hua (Barry Song)
2020-08-21 9:13 ` Song Bao Hua (Barry Song)
2020-08-21 9:13 ` Song Bao Hua (Barry Song)
2020-08-21 9:27 ` Will Deacon
2020-08-21 9:27 ` Will Deacon
2020-08-21 9:27 ` Will Deacon
2020-08-21 9:44 ` Song Bao Hua (Barry Song)
2020-08-21 9:44 ` Song Bao Hua (Barry Song)
2020-08-21 9:44 ` Song Bao Hua (Barry Song)
2020-08-21 2:26 ` [PATCH v6 2/2] arm64: mm: reserve per-numa CMA to localize coherent dma buffers Barry Song
2020-08-21 2:26 ` Barry Song
2020-08-21 2:26 ` Barry Song
2020-08-21 9:01 ` Will Deacon
2020-08-21 9:01 ` Will Deacon
2020-08-21 9:01 ` Will Deacon
2020-08-21 6:19 ` [PATCH v6 0/2] make dma_alloc_coherent NUMA-aware by per-NUMA CMA Christoph Hellwig
2020-08-21 6:19 ` Christoph Hellwig
2020-08-21 6:19 ` Christoph Hellwig
2020-08-21 8:10 ` Will Deacon
2020-08-21 8:10 ` Will Deacon
2020-08-21 8:10 ` Will Deacon
2020-08-31 8:23 ` Song Bao Hua (Barry Song)
2020-08-31 8:23 ` Song Bao Hua (Barry Song)
2020-08-31 8:23 ` Song Bao Hua (Barry Song)
2020-08-31 8:40 ` Christoph Hellwig [this message]
2020-08-31 8:40 ` Christoph Hellwig
2020-08-31 8:40 ` 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=20200831084018.GA903@lst.de \
--to=hch@lst.de \
--cc=catalin.marinas@arm.com \
--cc=ganapatrao.kulkarni@cavium.com \
--cc=huangdaode@huawei.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=robin.murphy@arm.com \
--cc=song.bao.hua@hisilicon.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.