netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Alexander Lobakin <alexandr.lobakin@intel.com>,
	Eric Dumazet <edumazet@google.com>,
	Alexander H Duyck <alexander.duyck@gmail.com>
Subject: Re: [PATCH net-next 0/2] gro: a couple of minor optimization
Date: Fri, 04 Feb 2022 12:34:03 +0100	[thread overview]
Message-ID: <be23f15d43f7af165c7d2121071b09be73740899.camel@redhat.com> (raw)
In-Reply-To: <cover.1643972527.git.pabeni@redhat.com>

On Fri, 2022-02-04 at 12:28 +0100, Paolo Abeni wrote:
> This series collects a couple of small optimizations for the GRO engine,
> reducing slightly the number of cycles for dev_gro_receive().
> The delta is within noise range in tput tests, but with big TCP coming
> every cycle saved from the GRO engine will count - I hope ;)
> 
> v1 -> v2:
>  - a few cleanup suggested from Alexander(s)
>  - moved away the more controversial 3rd patch
> 
> Paolo Abeni (2):
>   net: gro: avoid re-computing truesize twice on recycle
>   net: gro: minor optimization for dev_gro_receive()
> 
>  include/net/gro.h | 52 +++++++++++++++++++++++++----------------------
>  net/core/gro.c    | 16 ++++-----------
>  2 files changed, 32 insertions(+), 36 deletions(-)

This is really a v2. Please let me know if you prefer a formal repost.

Thanks!

Paolo


  parent reply	other threads:[~2022-02-04 11:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 11:28 [PATCH net-next 0/2] gro: a couple of minor optimization Paolo Abeni
2022-02-04 11:28 ` [PATCH net-next 1/2] net: gro: avoid re-computing truesize twice on recycle Paolo Abeni
2022-02-04 16:34   ` Eric Dumazet
2022-02-04 11:28 ` [PATCH net-next 2/2] net: gro: minor optimization for dev_gro_receive() Paolo Abeni
2022-02-04 11:34 ` Paolo Abeni [this message]
2022-02-05  9:51   ` [PATCH net-next 0/2] gro: a couple of minor optimization David Miller
2022-02-04 12:16 ` Alexander Lobakin
2022-02-04 15:55 ` Alexander Duyck
2022-02-05 15: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=be23f15d43f7af165c7d2121071b09be73740899.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=alexander.duyck@gmail.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).