Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 5 Jun 2023 15:58:23 +0200
From:   Richard Gobert <richardbgobert@gmail.com>
To:     Alexander Lobakin <aleksander.lobakin@intel.com>
Cc:     davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
        pabeni@redhat.com, lixiaoyan@google.com, lucien.xin@gmail.com,
        alexanderduyck@fb.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/1] gro: decrease size of CB
Message-ID: <20230605135821.GA8361@debian>
References: <20230601160924.GA9194@debian>
 <3f6cd784-767e-02e3-0c30-c0dda12e51ab@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3f6cd784-767e-02e3-0c30-c0dda12e51ab@intel.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

> I hope you've checked that there's no difference in object code with and
> w/o `inline`? Sometimes the compilers do weird things and stop inlining
> oneliners if they're used more than once. skb_gro_reset_offset() is
> marked `inline` exactly due to that =\

Checked on standard x86-64 and arm64 gcc compilers.
Would you check any other cases?