From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Cake] peeling harder with cake
Date: Fri, 3 Jul 2015 06:15:11 +0300 [thread overview]
Message-ID: <519B9F74-17B7-407D-9DAD-E5A0C610108D@gmail.com> (raw)
In-Reply-To: <CAA93jw4D9Z6-RqNPzgo1eUdW6_natr_Wj+oXCALetPGdzf75-Q@mail.gmail.com>
> On 3 Jul, 2015, at 04:27, Dave Taht <dave.taht@gmail.com> wrote:
>
> Also got more throughput for some reason.
Is the NIC doing software GSO or does it have hardware support? If the former, it would suggest that software GSO is a universally bad idea and should be excised. If the latter, GSO should be disabled full stop for this hardware, so we can stop fannying about with peeling.
- Jonathan Morton
next prev parent reply other threads:[~2015-07-03 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 1:27 [Cerowrt-devel] " Dave Taht
2015-07-03 3:15 ` Jonathan Morton [this message]
2015-07-03 16:01 ` [Cerowrt-devel] [Cake] " 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/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=519B9F74-17B7-407D-9DAD-E5A0C610108D@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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