From: Romain Gantois <romain.gantois@bootlin.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Romain Gantois <romain.gantois@bootlin.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Sylvain Girard <sylvain.girard@se.com>,
Pascal EBERHARD <pascal.eberhard@se.com>,
Richard Tresidder <rtresidd@electromag.com.au>,
Linus Walleij <linus.walleij@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH net v3 1/1] net: stmmac: Prevent DSA tags from breaking C
Date: Mon, 8 Jan 2024 15:23:38 +0100 (CET) [thread overview]
Message-ID: <3c2f6555-53b6-be1c-3d7b-7a6dc95b46fe@bootlin.com> (raw)
In-Reply-To: <20240108130238.j2denbdj3ifasbqi@skbuf>
On Mon, 8 Jan 2024, Vladimir Oltean wrote:
...
> Nitpick: you could render this in kernel-doc format.
> https://docs.kernel.org/doc-guide/kernel-doc.html
>
> > +static inline bool stmmac_has_ip_ethertype(struct sk_buff *skb)
>
> Nitpick: in netdev it is preferred not to use the "inline" keyword at
> all in C files, only "static inline" in headers, and to let the compiler
> decide by itself when it is appropriate to inline the code (which it
> does by itself even without the "inline" keyword). For a bit more
> background why, you can view Documentation/process/4.Coding.rst, section
> "Inline functions".
I see, the kernel docs were indeed enlightening on this point. As a side note,
I've just benchmarked both the "with-inline" and "without-inline" versions.
First of all, objdump seems to confirm that GCC does indeed follow this pragma
in this particular case. Also, RX perfs are better with stmmac_has_ip_ethertype
inlined, but TX perfs are actually consistently worse with this function
inlined, which could very well be caused by cache effects.
In any case, I think it is better to remove the "inline" pragma as you said.
I'll do that in v4.
Best Regards,
--
Romain Gantois, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-01-08 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 11:17 [PATCH net v3 0/1] Prevent DSA tags from breaking COE Romain Gantois
2024-01-08 11:17 ` [PATCH net v3 1/1] net: stmmac: " Romain Gantois
2024-01-08 13:02 ` Vladimir Oltean
2024-01-08 13:29 ` Miquel Raynal
2024-01-08 14:23 ` Romain Gantois [this message]
2024-01-08 14:36 ` [PATCH net v3 1/1] net: stmmac: Prevent DSA tags from breaking C Vladimir Oltean
2024-01-09 15:16 ` Romain Gantois
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=3c2f6555-53b6-be1c-3d7b-7a6dc95b46fe@bootlin.com \
--to=romain.gantois@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pascal.eberhard@se.com \
--cc=rtresidd@electromag.com.au \
--cc=stable@vger.kernel.org \
--cc=sylvain.girard@se.com \
--cc=vladimir.oltean@nxp.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).