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
Date: Mon, 5 Jun 2023 15:58:23 +0200 [thread overview]
Message-ID: <20230605135821.GA8361@debian> (raw)
In-Reply-To: <3f6cd784-767e-02e3-0c30-c0dda12e51ab@intel.com>
> 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?
next prev parent reply other threads:[~2023-06-05 13:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 16:09 [PATCH v3 0/1] gro: decrease size of CB Richard Gobert
2023-06-01 16:14 ` [PATCH v3 1/1] " Richard Gobert
2023-06-06 7:25 ` Eric Dumazet
2023-06-26 8:55 ` Gal Pressman
2023-06-27 14:21 ` David Ahern
2023-06-28 12:42 ` Gal Pressman
2023-06-28 14:19 ` David Ahern
2023-08-23 14:43 ` Gal Pressman
2023-08-24 3:31 ` David Ahern
2023-06-29 12:36 ` Richard Gobert
2023-06-29 13:04 ` Gal Pressman
2023-06-30 15:39 ` Richard Gobert
2023-07-02 14:41 ` Gal Pressman
2023-07-02 14:46 ` Gal Pressman
2023-07-03 14:23 ` Richard Gobert
2023-07-07 12:31 ` Richard Gobert
2023-07-09 6:55 ` Gal Pressman
2023-06-02 14:22 ` [PATCH v3 0/1] " Alexander Lobakin
2023-06-05 13:58 ` Richard Gobert [this message]
2023-06-06 13:24 ` Alexander Lobakin
2023-06-06 9:20 ` patchwork-bot+netdevbpf
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=20230605135821.GA8361@debian \
--to=richardbgobert@gmail.com \
--cc=aleksander.lobakin@intel.com \
--cc=alexanderduyck@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.