From: patchwork-bot+netdevbpf@kernel.org
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxarm@openeuler.org,
hawk@kernel.org, ilias.apalodimas@linaro.org,
akpm@linux-foundation.org, peterz@infradead.org, will@kernel.org,
jhubbard@nvidia.com, yuzhao@google.com, mcroce@microsoft.com,
fenghua.yu@intel.com, feng.tang@intel.com, jgg@ziepe.ca,
aarcange@redhat.com, guro@fb.com
Subject: Re: [PATCH net-next v6] page_pool: disable dma mapping support for 32-bit arch with 64-bit DMA
Date: Fri, 15 Oct 2021 10:00:07 +0000 [thread overview]
Message-ID: <163429200757.18650.14587453476284432970.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211013091920.1106-1-linyunsheng@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 13 Oct 2021 17:19:20 +0800 you wrote:
> As the 32-bit arch with 64-bit DMA seems to rare those days,
> and page pool might carry a lot of code and complexity for
> systems that possibly.
>
> So disable dma mapping support for such systems, if drivers
> really want to work on such systems, they have to implement
> their own DMA-mapping fallback tracking outside page_pool.
>
> [...]
Here is the summary with links:
- [net-next,v6] page_pool: disable dma mapping support for 32-bit arch with 64-bit DMA
https://git.kernel.org/netdev/net-next/c/d00e60ee54b1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-10-15 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 9:19 [PATCH net-next v6] page_pool: disable dma mapping support for 32-bit arch with 64-bit DMA Yunsheng Lin
2021-10-13 10:21 ` Jesper Dangaard Brouer
2021-10-15 10:00 ` patchwork-bot+netdevbpf [this message]
2021-11-09 9:58 ` Guillaume Tucker
2021-11-09 12:02 ` Yunsheng Lin
2021-11-12 9:21 ` Guillaume Tucker
2021-11-15 3:34 ` Yunsheng Lin
2021-11-15 11:53 ` Ilias Apalodimas
2021-11-15 12:10 ` Ilias Apalodimas
2021-11-15 12:21 ` Yunsheng Lin
2021-11-15 14:39 ` Jesper Dangaard Brouer
2021-11-15 18:55 ` Ilias Apalodimas
2021-11-17 11:52 ` Jesper Dangaard Brouer
2021-11-15 17:59 ` Christoph Hellwig
2021-11-15 18:48 ` Ilias Apalodimas
2021-11-15 18:53 ` 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=163429200757.18650.14587453476284432970.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=feng.tang@intel.com \
--cc=fenghua.yu@intel.com \
--cc=guro@fb.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=linyunsheng@huawei.com \
--cc=mcroce@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=yuzhao@google.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