From: patchwork-bot+netdevbpf@kernel.org
To: Florian Schauer <florian@schauer.to>
Cc: hawk@kernel.org, ilias.apalodimas@linaro.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, sdf@fomichev.me,
linyunsheng@huawei.com
Subject: Re: [PATCH net v2] page_pool: keep frag_offset aligned for odd-sized requests
Date: Tue, 01 Sep 2026 00:00:10 +0000 [thread overview]
Message-ID: <178822081064.841883.3266545254539695421.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260828060822.2628276-1-florian@schauer.to>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Aug 2026 08:08:22 +0200 you wrote:
> page_pool_alloc_frag_netmem() rounds the requested fragment size with
>
> size = ALIGN(size, dma_get_cache_alignment());
>
> dma_get_cache_alignment() returns 1 unless the architecture defines
> ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not.
> There the ALIGN() is a no-op and pool->frag_offset advances by the raw,
> unrounded size.
>
> [...]
Here is the summary with links:
- [net,v2] page_pool: keep frag_offset aligned for odd-sized requests
https://git.kernel.org/netdev/net/c/dc0df5a0c62c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-01 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 6:08 [PATCH net v2] page_pool: keep frag_offset aligned for odd-sized requests Florian Schauer
2026-08-30 21:23 ` Fabricio Gava
2026-08-30 22:11 ` Bruno Xavier
2026-08-31 9:00 ` Jesper Dangaard Brouer
2026-08-31 9:42 ` Eric Dumazet
2026-09-01 0:00 ` patchwork-bot+netdevbpf [this message]
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=178822081064.841883.3266545254539695421.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian@schauer.to \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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