From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, edumazet@google.com, davem@davemloft.net,
kuba@kernel.org, horms@kernel.org, andrew+netdev@lunn.ch,
alexanderduyck@fb.com, razor@blackwall.org,
kernelxing@tencent.com
Subject: Re: [PATCH v2 net 0/2] net: remove the single page frag cache for good
Date: Thu, 20 Feb 2025 10:10:30 +0000 [thread overview]
Message-ID: <174004623026.1237752.7422488683679437676.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1739899357.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 18 Feb 2025 19:29:38 +0100 you wrote:
> This is another attempt at reverting commit dbae2b062824 ("net: skb:
> introduce and use a single page frag cache"), as it causes regressions
> in specific use-cases.
>
> Reverting such commit uncovers an allocation issue for build with
> CONFIG_MAX_SKB_FRAGS=45, as reported by Sabrina.
>
> [...]
Here is the summary with links:
- [v2,net,1/2] net: allow small head cache usage with large MAX_SKB_FRAGS values
https://git.kernel.org/netdev/net/c/14ad6ed30a10
- [v2,net,2/2] Revert "net: skb: introduce and use a single page frag cache"
https://git.kernel.org/netdev/net/c/6bc7e4eb0499
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:[~2025-02-20 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 18:29 [PATCH v2 net 0/2] net: remove the single page frag cache for good Paolo Abeni
2025-02-18 18:29 ` [PATCH v2 net 1/2] net: allow small head cache usage with large MAX_SKB_FRAGS values Paolo Abeni
2025-02-20 9:41 ` Eric Dumazet
2025-02-18 18:29 ` [PATCH v2 net 2/2] Revert "net: skb: introduce and use a single page frag cache" Paolo Abeni
2025-02-20 9:41 ` Eric Dumazet
2025-02-20 10:10 ` 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=174004623026.1237752.7422488683679437676.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.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.