From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: edumazet@google.com, pablo@netfilter.org, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net, horms@kernel.org,
aleksander.lobakin@intel.com, netdev@vger.kernel.org,
kernelxing@tencent.com
Subject: Re: [PATCH net-next v2] net: save some cycles when doing skb_attempt_defer_free()
Date: Mon, 15 Apr 2024 09:40:28 +0000 [thread overview]
Message-ID: <171317402855.10544.4488096610959172943.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240412030718.68016-1-kerneljasonxing@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 12 Apr 2024 11:07:18 +0800 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
>
> Normally, we don't face these two exceptions very often meanwhile
> we have some chance to meet the condition where the current cpu id
> is the same as skb->alloc_cpu.
>
> One simple test that can help us see the frequency of this statement
> 'cpu == raw_smp_processor_id()':
> 1. running iperf -s and iperf -c [ip] -P [MAX CPU]
> 2. using BPF to capture skb_attempt_defer_free()
>
> [...]
Here is the summary with links:
- [net-next,v2] net: save some cycles when doing skb_attempt_defer_free()
https://git.kernel.org/netdev/net-next/c/4d0470b9ad73
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:[~2024-04-15 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 3:07 [PATCH net-next v2] net: save some cycles when doing skb_attempt_defer_free() Jason Xing
2024-04-15 9:40 ` 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=171317402855.10544.4488096610959172943.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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.