From: "Toke Høiland-Jørgensen" <toke@redhat•com>
To: Eric Dumazet <edumazet@google•com>,
"David S . Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>
Cc: Simon Horman <horms@kernel•org>,
Jamal Hadi Salim <jhs@mojatatu•com>,
Cong Wang <xiyou.wangcong@gmail•com>,
Jiri Pirko <jiri@resnulli•us>,
Kuniyuki Iwashima <kuniyu@google•com>,
Willem de Bruijn <willemb@google•com>,
netdev@vger•kernel.org, eric.dumazet@gmail•com,
Eric Dumazet <edumazet@google•com>
Subject: Re: [PATCH v2 net-next 2/6] net: add add indirect call wrapper in skb_release_head_state()
Date: Wed, 15 Oct 2025 10:17:22 +0200 [thread overview]
Message-ID: <87v7kgfujx.fsf@toke.dk> (raw)
In-Reply-To: <20251014171907.3554413-3-edumazet@google.com>
Eric Dumazet <edumazet@google•com> writes:
> While stress testing UDP senders on a host with expensive indirect
> calls, I found cpus processing TX completions where showing
> a very high cost (20%) in sock_wfree() due to
> CONFIG_MITIGATION_RETPOLINE=y.
>
> Take care of TCP and UDP TX destructors and use INDIRECT_CALL_3() macro.
>
> Signed-off-by: Eric Dumazet <edumazet@google•com>
Reviewed-by: Toke Høiland-Jørgensen <toke@redhat•com>
next prev parent reply other threads:[~2025-10-15 8:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 17:19 [PATCH v2 net-next 0/6] net: optimize TX throughput and efficiency Eric Dumazet
2025-10-14 17:19 ` [PATCH v2 net-next 1/6] selftests/net: packetdrill: unflake tcp_user_timeout_user-timeout-probe.pkt Eric Dumazet
2025-10-15 5:54 ` Kuniyuki Iwashima
2025-10-14 17:19 ` [PATCH v2 net-next 2/6] net: add add indirect call wrapper in skb_release_head_state() Eric Dumazet
2025-10-15 3:57 ` Kuniyuki Iwashima
2025-10-15 8:17 ` Toke Høiland-Jørgensen [this message]
2025-10-15 12:02 ` Alexander Lobakin
2025-10-15 12:16 ` Eric Dumazet
2025-10-15 12:30 ` Alexander Lobakin
2025-10-15 12:46 ` Eric Dumazet
2025-10-15 12:49 ` Eric Dumazet
2025-10-15 12:54 ` Alexander Lobakin
2025-10-15 13:01 ` Eric Dumazet
2025-10-15 13:08 ` Alexander Lobakin
2025-10-15 13:11 ` Eric Dumazet
2025-10-20 7:01 ` Jason Xing
2025-10-20 7:41 ` Eric Dumazet
2025-10-20 9:14 ` Jason Xing
2025-10-14 17:19 ` [PATCH v2 net-next 3/6] net/sched: act_mirred: add loop detection Eric Dumazet
2025-10-15 5:24 ` Kuniyuki Iwashima
2025-10-15 8:17 ` Toke Høiland-Jørgensen
2025-10-14 17:19 ` [PATCH v2 net-next 4/6] Revert "net/sched: Fix mirred deadlock on device recursion" Eric Dumazet
2025-10-15 5:26 ` Kuniyuki Iwashima
2025-10-15 8:17 ` Toke Høiland-Jørgensen
2025-10-16 12:03 ` Victor Nogueira
2025-10-14 17:19 ` [PATCH v2 net-next 5/6] net: sched: claim one cache line in Qdisc Eric Dumazet
2025-10-15 5:42 ` Kuniyuki Iwashima
2025-10-15 8:17 ` Toke Høiland-Jørgensen
2025-10-14 17:19 ` [PATCH v2 net-next 6/6] net: dev_queue_xmit() llist adoption Eric Dumazet
2025-10-15 6:20 ` Kuniyuki Iwashima
2025-10-15 22:00 ` [PATCH v2 net-next 0/6] net: optimize TX throughput and efficiency Jamal Hadi Salim
2025-10-15 22:11 ` Eric Dumazet
2025-10-16 23:50 ` patchwork-bot+netdevbpf
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=87v7kgfujx.fsf@toke.dk \
--to=toke@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=kuniyu@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=willemb@google$(echo .)com \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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