From: Jonathan Morton <chromatix99@gmail.com>
To: Alan Jenkins <alan.christopher.jenkins@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] openwrt build with latest cake and other qdiscs
Date: Thu, 14 May 2015 13:42:55 +0300 [thread overview]
Message-ID: <51BC816B-2177-4EB2-921B-AA91345ADF2A@gmail.com> (raw)
In-Reply-To: <555479DE.90806@gmail.com>
> On 14 May, 2015, at 13:33, Alan Jenkins <alan.christopher.jenkins@gmail.com> wrote:
>
> On 14/05/15 11:24, Jonathan Morton wrote:
>> I can’t figure out the connection between HTB and that code. Also,
>> that appears to be GSO, not GRO. I’m not precisely sure what the
>> difference is, but I’d hazard a guess that GSO is outbound, GRO is
>> inbound.
>
> I've just been reading thanks to Seb. GSO is outbound. GRO is inbound.
>
> They appear to interact in routing: if you GRO packets, you end up with >MTU skbs, which then *have* to be de-aggregated somehow before you can send them.
>
> (And the popular reference on GRO is https://lwn.net/Articles/358910/).
Which says that GSO can resegment GRO chunks. Hmm.
Are we typically getting GRO in CPE devices?
- Jonathan Morton
next prev parent reply other threads:[~2015-05-14 10:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 14:02 Alan Jenkins
2015-05-10 17:29 ` Alan Jenkins
2015-05-10 20:37 ` Dave Taht
2015-05-10 20:38 ` Dave Taht
2015-05-11 6:54 ` Sebastian Moeller
2015-05-10 21:46 ` Sebastian Moeller
2015-05-10 22:19 ` Dave Taht
2015-05-11 6:50 ` Sebastian Moeller
2015-05-11 7:01 ` Jonathan Morton
2015-05-13 6:43 ` Jonathan Morton
2015-05-14 9:19 ` Sebastian Moeller
2015-05-14 10:24 ` Jonathan Morton
2015-05-14 10:33 ` Alan Jenkins
2015-05-14 10:42 ` Jonathan Morton [this message]
2015-05-14 10:58 ` Sebastian Moeller
2015-05-14 13:12 ` Jonathan Morton
2015-05-14 14:57 ` Sebastian Moeller
2015-05-14 15:32 ` Jonathan Morton
2015-05-14 18:15 ` Sebastian Moeller
2015-05-14 22:06 ` Jonathan Morton
2015-05-15 2:27 ` Dave Taht
2015-05-15 21:49 ` Jonathan Morton
2015-05-14 9:50 ` Alan Jenkins
2015-05-18 0:49 ` [Cake] More overhead keywords Jonathan Morton
2015-05-18 7:27 ` Sebastian Moeller
2015-05-18 8:13 ` Jonathan Morton
2015-05-18 8:41 ` Sebastian Moeller
2015-05-18 19:41 ` David Lang
2015-05-18 19:57 ` Dave Taht
2015-05-19 10:14 ` Kevin Darbyshire-Bryant
2015-05-23 0:30 ` Dave Taht
2015-05-23 2:27 ` Jonathan Morton
-- strict thread matches above, loose matches on Subject: below --
2015-05-05 8:50 [Cake] openwrt build with latest cake and other qdiscs Dave Taht
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=51BC816B-2177-4EB2-921B-AA91345ADF2A@gmail.com \
--to=chromatix99@gmail.com \
--cc=alan.christopher.jenkins@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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