All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	victor@mojatatu.com, pctammela@mojatatu.ai
Subject: Re: [PATCH net-next] net/sched: refine indirect call mitigation in tc_wrapper.h
Date: Tue, 10 Mar 2026 03:00:37 +0000	[thread overview]
Message-ID: <177311163779.2039470.9221132616218172490.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260307133601.3863071-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sat,  7 Mar 2026 13:36:01 +0000 you wrote:
> Some modern cpus disable X86_FEATURE_RETPOLINE feature,
> even if a direct call can still be beneficial.
> 
> Even when IBRS is present, an indirect call is more expensive
> than a direct one:
> 
> Direct Calls:
>   Compilers can perform powerful optimizations like inlining,
>   where the function body is directly inserted at the call site,
>   eliminating call overhead entirely.
> 
> [...]

Here is the summary with links:
  - [net-next] net/sched: refine indirect call mitigation in tc_wrapper.h
    https://git.kernel.org/netdev/net-next/c/f2db7b80b03f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-03-10  3:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 13:36 [PATCH net-next] net/sched: refine indirect call mitigation in tc_wrapper.h Eric Dumazet
2026-03-07 21:44 ` Jamal Hadi Salim
2026-03-07 23:53   ` Eric Dumazet
2026-03-09 16:19     ` Jamal Hadi Salim
2026-03-09 17:37 ` Pedro Tammela
2026-03-09 18:34 ` Victor Nogueira
2026-03-10  3: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=177311163779.2039470.9221132616218172490.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pctammela@mojatatu.ai \
    --cc=victor@mojatatu.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 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.