mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Yue Haibing <yuehaibing@huawei.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<horms@kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] ipv6: sit: Add ipip6_tunnel_dst_find() for cleanup
Date: Thu, 28 Aug 2025 17:33:36 +0200	[thread overview]
Message-ID: <56aac06f-45b6-4a3c-9436-f400a4efd3d5@intel.com> (raw)
In-Reply-To: <83aeba1c-27ff-4a92-b91e-5719be879e7a@huawei.com>

From: Yue Haibing <yuehaibing@huawei.com>
Date: Thu, 28 Aug 2025 14:44:07 +0800

> On 2025/8/28 14:13, Yue Haibing wrote:
>> On 2025/8/27 22:45, Alexander Lobakin wrote:
>>> From: Yue Haibing <yuehaibing@huawei.com>
>>> Date: Wed, 27 Aug 2025 12:00:27 +0800
>>>
>>>> Extract the dst lookup logic from ipip6_tunnel_xmit() into new helper
>>>> ipip6_tunnel_dst_find() to reduce code duplication and enhance readability.
>>>>
>>>> No functional change intended.
>>>
>>> ...but bloat-o-meter stats would be nice to see here. I'm curious
>>> whether the object code got any changes or the compilers still just
>>> inline this function to both call sites.
> 
> On a x86_64, with allmodconfig:
> 
> ./scripts/bloat-o-meter -c net/ipv6/sit.o net/ipv6/sit-after.o
> add/remove: 2/0 grow/shrink: 1/1 up/down: 1770/-2152 (-382)
> Function                                     old     new   delta
> ipip6_tunnel_dst_find                          -    1697   +1697
> __pfx_ipip6_tunnel_dst_find                    -      64     +64
> ipip6_tunnel_xmit.isra.cold                   79      88      +9
> ipip6_tunnel_xmit.isra                      9910    7758   -2152

Oh okay, so it doesn't inline the function due to its size. Maybe it's
even better since we have a good object code reduction now and that
branch inside the func shouldn't hurt the performance much.

> Total: Before=70060, After=69678, chg -0.55%

Thanks,
Olek

      reply	other threads:[~2025-08-28 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27  4:00 Yue Haibing
2025-08-27 14:45 ` Alexander Lobakin
2025-08-28  6:13   ` Yue Haibing
2025-08-28  6:44     ` Yue Haibing
2025-08-28 15:33       ` Alexander Lobakin [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=56aac06f-45b6-4a3c-9436-f400a4efd3d5@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yuehaibing@huawei.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

all inboxes | Powered by JetHome®