netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, kuniyu@amazon.com
Subject: Re: [PATCH net-next v2 1/3] net/sched: add retpoline wrapper for tc
Date: Fri, 2 Dec 2022 10:13:31 -0800	[thread overview]
Message-ID: <20221202101331.178f0bcb@kernel.org> (raw)
In-Reply-To: <d2455b9f-78a3-81fe-46d5-c7aa03879294@mojatatu.com>

On Fri, 2 Dec 2022 09:48:49 -0300 Pedro Tammela wrote:
> > Most definitely not to this reader :) The less macro magic the better.
> > I'm primarily curious about whether the compiler treats this sort of
> > construct the same as a switch.  
> 
> Apparently we can't do a switch case in pointer addresses because the 
> case condition must be constant.

Ack, thanks for checking!

  reply	other threads:[~2022-12-02 18:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 15:44 [PATCH net-next v2 0/3] net/sched: retpoline wrappers for tc Pedro Tammela
2022-11-28 15:44 ` [PATCH net-next v2 1/3] net/sched: add retpoline wrapper " Pedro Tammela
2022-12-01  5:16   ` Jakub Kicinski
2022-12-01 16:40     ` Pedro Tammela
2022-12-01 22:38       ` Jakub Kicinski
2022-12-02 12:48         ` Pedro Tammela
2022-12-02 18:13           ` Jakub Kicinski [this message]
2022-12-01 11:10   ` Paolo Abeni
2022-12-05  4:56   ` Eric Dumazet
2022-11-28 15:44 ` [PATCH net-next v2 2/3] net/sched: avoid indirect act functions on retpoline kernels Pedro Tammela
2022-11-28 15:44 ` [PATCH net-next v2 3/3] net/sched: avoid indirect classify " Pedro Tammela
2022-12-01 11:05 ` [PATCH net-next v2 0/3] net/sched: retpoline wrappers for tc Paolo Abeni
2022-12-01 12:34   ` Jamal Hadi Salim
2022-12-04 23:13     ` Pedro Tammela

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=20221202101331.178f0bcb@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pctammela@mojatatu.com \
    --cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).