From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
Jiri Benc <jbenc@redhat.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
Paolo Abeni <pabeni@redhat.com>, Netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jesse Gross <jesse@kernel.org>, Tom Herbert <tom@herbertland.com>
Subject: Re: [PATCH net-next 0/4] net: cleanup for UDP tunnel's GRO
Date: Sat, 9 Jul 2016 18:18:16 +0300 [thread overview]
Message-ID: <20160709181816.1f601239@halley> (raw)
In-Reply-To: <1dc81b88-47c9-4274-6275-490b16526d4a@stressinduktion.org>
On Fri, 8 Jul 2016 19:04:27 -0400 Hannes Frederic Sowa <hannes@stressinduktion.org> wrote:
> >> I really do wonder if GRO on top of fragmentation does have any effect.
> >> Would be great if someone has data for that already?
> >
> > I think that logic is kind of backwards. It is already there.
> > Instead of asking people to prove that this change is invalid the onus
> > should be on the submitter to prove the change causes no harm.
>
> Of course, sorry, I didn't want to make the impression others should do
> that. I asked because Shmulik made the impression on me he had
> experience with GRO+fragmentation on vxlan and/or geneve and could
> provide some data, maybe even just anecdotal.
Few anecdotal updates.
I don't have ready-made data as the systems are not using this exact
kind of of setup.
However, by performing some quick experimentations, it reveals that GRO
on top of the tunnels, where tunnel datagrams are fragmented, has some
effect. The packets indeed get aggregated, although not aggresively as
in the non-fragmented case.
Whether the effect is significant depends on the system.
In a system that is very sensitive to non-aggregated skbs (due to a cpu
bottleneck during further processing of the decapsulated packets), the
effect of aggregation is indeed significant.
Regards,
Shmulik
next prev parent reply other threads:[~2016-07-09 15:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 15:58 [PATCH net-next 0/4] net: cleanup for UDP tunnel's GRO Paolo Abeni
2016-07-08 16:21 ` Alexander Duyck
2016-07-08 20:17 ` Shmulik Ladkani
2016-07-08 20:57 ` Hannes Frederic Sowa
2016-07-08 21:19 ` Shmulik Ladkani
2016-07-08 21:40 ` Hannes Frederic Sowa
2016-07-08 21:27 ` Alexander Duyck
2016-07-08 21:51 ` Hannes Frederic Sowa
2016-07-08 22:11 ` Alexander Duyck
2016-07-08 23:04 ` Hannes Frederic Sowa
2016-07-09 1:27 ` Alexander Duyck
2016-07-09 15:18 ` Shmulik Ladkani [this message]
2016-07-09 15:35 ` Hannes Frederic Sowa
2016-07-09 15:56 ` Shmulik Ladkani
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=20160709181816.1f601239@halley \
--to=shmulik.ladkani@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jbenc@redhat.com \
--cc=jesse@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tom@herbertland.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).