From: Florian Westphal <fw@strlen.de>
To: Eric Dumazet <edumazet@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Nicolas Pitre <npitre@baylibre.com>
Subject: Re: [PATCH] compiler_types: Introduce inline_for_performance
Date: Sun, 18 Jan 2026 16:32:05 +0100 [thread overview]
Message-ID: <aWz89X0y6UNH59I7@strlen.de> (raw)
In-Reply-To: <20260118152448.2560414-1-edumazet@google.com>
Eric Dumazet <edumazet@google.com> wrote:
> -#ifdef CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE
> -static __always_inline
> -#else
> -static inline
> -#endif
> +static inline_for_performance
..
> -#ifdef CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE
> -static __always_inline
> -#else
> -static inline
> -#endif
> +static inline_for_performance
..
> +#ifdef CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE
> +#define inline_for_performance __always_inline
> +#else
> +#define inline_for_performance
> +#endif
Should that read
#else
+#define inline_for_performance inline
instead?
next prev parent reply other threads:[~2026-01-18 15:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 15:24 [PATCH] compiler_types: Introduce inline_for_performance Eric Dumazet
2026-01-18 15:32 ` Florian Westphal [this message]
2026-01-18 15:39 ` Eric Dumazet
2026-01-18 18:36 ` kernel test robot
2026-01-18 22:33 ` David Laight
2026-01-18 19:47 ` Andrew Morton
2026-01-18 20:38 ` Eric Dumazet
2026-01-18 22:58 ` David Laight
2026-01-19 0:01 ` Andrew Morton
2026-01-19 9:33 ` David Laight
2026-01-19 10:25 ` Eric Dumazet
2026-01-19 10:33 ` Eric Dumazet
2026-01-19 10:50 ` David Laight
2026-01-19 15:47 ` Nicolas Pitre
2026-01-19 19:03 ` David Laight
2026-01-19 19:44 ` Nicolas Pitre
2026-01-18 21:04 ` kernel test robot
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=aWz89X0y6UNH59I7@strlen.de \
--to=fw@strlen.de \
--cc=akpm@linux-foundation.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=npitre@baylibre.com \
--cc=pabeni@redhat.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