From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Peeling question
Date: Thu, 27 Aug 2015 08:25:39 +0300 [thread overview]
Message-ID: <CAJq5cE1Ty_vb5TpC0VvD9zb-hGugry3UkPhkRsfYKy2LSRsyww@mail.gmail.com> (raw)
In-Reply-To: <E8B8D732-3EFC-486D-BC8F-C69D0FB776F6@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
I'm not *absolutely* sure that the following is correct - I'm extrapolating
a little.
Except to say that GSO and GRO have zero impact on packet format or size on
the wire (unlike jumbo frames). It's entirely reasonable for packets sent
with GSO to be received without GRO and vice versa. Of that I am certain.
Interfaces that don't support GSO, or where it is turned off, will
automatically receive only individual packets. You can examine this
capability using ethtool, which works fine on wifi interfaces as well as
genuine Ethernet.
I haven't tried ethtool on PPP-anything, but I wouldn't expect to see
support for offloads there. If for some reason it is there, by all means
turn it off.
Probably the easiest way to observe GSO in action it to run Codel or
fq_codel on the relevant interfaces, without shaping, and put a heavy but
simple TCP load, such as nttcp, through it. Watch the maxpacket stat in tc
-s qdisc. Some hardware is more aggressive than others.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 1135 bytes --]
prev parent reply other threads:[~2015-08-27 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 14:52 Sebastian Moeller
2015-08-27 5:25 ` Jonathan Morton [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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJq5cE1Ty_vb5TpC0VvD9zb-hGugry3UkPhkRsfYKy2LSRsyww@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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