From: "Malladi, Meghana" <m-malladi@ti.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: <rogerq@kernel.org>, <danishanwar@ti.com>, <pabeni@redhat.com>,
<kuba@kernel.org>, <edumazet@google.com>, <davem@davemloft.net>,
<andrew+netdev@lunn.ch>, <bpf@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<u.kleine-koenig@baylibre.com>,
<matthias.schiffer@ew.tq-group.com>, <schnelle@linux.ibm.com>,
<diogo.ivo@siemens.com>, <glaroque@baylibre.com>,
<macro@orcam.me.uk>, <john.fastabend@gmail.com>,
<hawk@kernel.org>, <daniel@iogearbox.net>, <ast@kernel.org>,
<srk@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH net-next v3 3/3] net: ti: icssg-prueth: Add XDP support
Date: Wed, 5 Mar 2025 14:53:07 +0530 [thread overview]
Message-ID: <fd989751-e7f6-40bb-a0bf-058c752cc7bc@ti.com> (raw)
In-Reply-To: <61117a07-35b5-48c0-93d9-f97db8e15503@stanley.mountain>
Hi Dan,
On 3/3/2025 7:38 PM, Dan Carpenter wrote:
> What I mean is just compile the .o file with and without the unlikely().
> $ md5sum drivers/net/ethernet/ti/icssg/icssg_common. o*
> 2de875935222b9ecd8483e61848c4fc9 drivers/net/ethernet/ti/icssg/
> icssg_common. o. annotation 2de875935222b9ecd8483e61848c4fc9
> ZjQcmQRYFpfptBannerStart
> This message was sent from outside of Texas Instruments.
> Do not click links or open attachments unless you recognize the source
> of this email and know the content is safe.
> Report Suspicious
> <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/G3vK!
> uldq3TevVoc7KuXEXHnDf-
> TXtuZ0bON9iO0jTE7PyIS1jjfs_CzpvIiMi93PVt0MVDzjHGQSK__vY_-6rO7q86rFmBMGW4SSqK5pvNE$>
> ZjQcmQRYFpfptBannerEnd
>
> What I mean is just compile the .o file with and without the unlikely().
>
> $ md5sum drivers/net/ethernet/ti/icssg/icssg_common.o*
> 2de875935222b9ecd8483e61848c4fc9 drivers/net/ethernet/ti/icssg/icssg_common.o.annotation
> 2de875935222b9ecd8483e61848c4fc9 drivers/net/ethernet/ti/icssg/icssg_common.o.no_anotation
>
> Generally the rule is that you should leave likely/unlikely() annotations
> out unless it's going to make a difference on a benchmark. I'm not going
> to jump down people's throat about this, and if you want to leave it,
> it's fine. But it just struct me as weird so that's why I commented on
> it.
>
I have done some performance tests to see if unlikely() is gonna make
any impact and I see around ~9000 pps and 6Mbps drop without unlikely()
for small packet sizes (60 Bytes)
You can see summary of the tests here:
packet size with unlikely(pps) without unlikely(pps) regression
60 462377 453251 9126
80 403020 399372 3648
96 402059 396881 5178
120 392725 391312 4413
140 327706 327099 607
packet size with unlikely(Mbps) without unlikely(Mbps) regression
60 311 305 6
80 335 332 3
96 386 381 5
120 456 451 5
140 430 429 1
For more details on the logs, please
refer:https://gist.github.com/MeghanaMalladiTI/cc6cc7709791376cb486eb1222de67be
Regards,
Meghana Malladi
> regards,
> dan carpenter
>
> diff --git a/drivers/net/ethernet/ti/icssg/icssg_common.c b/drivers/net/ethernet/ti/icssg/icssg_common.c
> index 34d16e00c2ec..3db5bae44e61 100644
> --- a/drivers/net/ethernet/ti/icssg/icssg_common.c
> +++ b/drivers/net/ethernet/ti/icssg/icssg_common.c
> @@ -672,7 +672,7 @@ static int emac_run_xdp(struct prueth_emac *emac, struct xdp_buff *xdp,
> case XDP_TX:
> /* Send packet to TX ring for immediate transmission */
> xdpf = xdp_convert_buff_to_frame(xdp);
> - if (unlikely(!xdpf))
> + if (!xdpf)
> goto drop;
>
> q_idx = smp_processor_id() % emac->tx_ch_num;
>
next prev parent reply other threads:[~2025-03-05 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 11:00 [PATCH net-next v3 0/3] net: ti: icssg-prueth: Add native mode XDP support Meghana Malladi
2025-02-24 11:01 ` [PATCH net-next v3 1/3] net: ti: icssg-prueth: Use page_pool API for RX buffer allocation Meghana Malladi
2025-02-24 14:20 ` Roger Quadros
2025-03-03 11:16 ` Malladi, Meghana
2025-02-24 11:01 ` [PATCH net-next v3 2/3] net: ti: icssg-prueth: introduce and use prueth_swdata struct for SWDATA Meghana Malladi
2025-02-26 10:29 ` Dan Carpenter
2025-03-03 11:49 ` [EXTERNAL] " Malladi, Meghana
2025-02-27 12:27 ` Roger Quadros
2025-03-03 11:23 ` Malladi, Meghana
2025-02-24 11:01 ` [PATCH net-next v3 3/3] net: ti: icssg-prueth: Add XDP support Meghana Malladi
2025-02-26 10:49 ` Dan Carpenter
2025-03-03 12:06 ` [EXTERNAL] " Malladi, Meghana
2025-03-03 12:31 ` Dan Carpenter
2025-03-03 13:36 ` Malladi, Meghana
2025-03-03 14:08 ` Dan Carpenter
2025-03-05 9:23 ` Malladi, Meghana [this message]
2025-03-05 9:31 ` Dan Carpenter
2025-02-27 15:37 ` Roger Quadros
2025-03-03 11:36 ` Malladi, Meghana
2025-02-24 13:35 ` [PATCH net-next v3 0/3] net: ti: icssg-prueth: Add native mode " Diogo Ivo
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=fd989751-e7f6-40bb-a0bf-058c752cc7bc@ti.com \
--to=m-malladi@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=daniel@iogearbox.net \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=glaroque@baylibre.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=schnelle@linux.ibm.com \
--cc=srk@ti.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vigneshr@ti.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).