From: Dave Taht <dave.taht@gmail.com>
To: Eric Dumazet <edumazet@google.com>,
cake@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Peeling GRO
Date: Tue, 28 Apr 2015 15:12:23 -0700 [thread overview]
Message-ID: <CAA93jw4VDC9iipd-GC1=MFn2wVW8LeK-jB4C2PzVnAjyRYxj6w@mail.gmail.com> (raw)
On Tue, Apr 28, 2015 at 3:04 PM, Eric Dumazet <edumazet@google.com> wrote:
> This what we do in net/sched/sch_tbf.c (search for tbf_segment())
Thank you! I had no idea that what I had been calling peeling already
existed. Perhaps in the simplest.qos model in the sqm-scripts (only
one sub qdisc) we should try tbf instead of htb?
> Although this is quite expensive, this is doable.
Turning off GRO universally is also expensive (in terms of costs to
other devices that are not rate limited, and in terms of actually
getting it right in the first place)
the mvneta dropped from 720Mbit each way to 320 with offloads off. We
have had similar trouble with the ubnt edgerouters (8 ports worth of
offloads).
We were mostly struggling with stuff
at very low rates < 60Mbit, now we are struggling with 100-300Mbit inbound....
>
>
>
> On Tue, Apr 28, 2015 at 2:38 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> Dear Eric:
>>
>> how would you go about peeling apart a TSO/GSO/GRO packet in a qdisc,
>> and then serving up one packet (or drr quantum's worth) of packets?
>>
>> I am seeing 64K GRO'd packets from mvneta driver in the linksys 1900ac
>> device in particular.
>>
>> ---------- Forwarded message ----------
>> From: Dave Taht <dave.taht@gmail.com>
>> Date: Tue, Apr 28, 2015 at 11:04 AM
>> Subject: documentation review request and out of tree cake builds for
>> openwrt/etc.
>> To: cake@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>,
>> "cerowrt-devel@lists.bufferbloat.net"
>> <cerowrt-devel@lists.bufferbloat.net>
>>
>>
>> 1) I have burned much of the morning updating this:
>>
>> http://www.bufferbloat.net/projects/codel/wiki/Cake
>>
>> Reviewers wanted.
>>
>> 2) I am not sure of the right configuration to push stuff to the
>> iproute2-cake repo (removing sfq_codel, and there is an important
>> bugfix in the mainline iproute2 that needs to be pushed into it)
>>
>> 3) I have pushed support for building cake out of tree in openwrt to
>> the ceropackages repo (for now), but have not created a new
>> iproute2-cake for it due to item 2. My intent would be to get both
>> into openwrt chaos calmer for further testing... in some repo or
>> another that wasn't ceropackages. the routing repo?
>>
>> 4) http://www.dslreports.com/forum/news,133536~fmode=flat~days=2000
>> has some good convo going on also.
>>
>> --
>> Dave Täht
>> Open Networking needs **Open Source Hardware**
>>
>> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
>>
>>
>> --
>> Dave Täht
>> Open Networking needs **Open Source Hardware**
>>
>> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
>
>
--
Dave Täht
Open Networking needs **Open Source Hardware**
https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
next reply other threads:[~2015-04-28 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 22:12 Dave Taht [this message]
2015-04-28 22:16 ` Eric Dumazet
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4VDC9iipd-GC1=MFn2wVW8LeK-jB4C2PzVnAjyRYxj6w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=edumazet@google.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