Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@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 09:01:08 -0700	[thread overview]
Message-ID: <CAA93jw438n_efq+y-nSRz0+15Vx0e33PJ47DMOEXQ866rsww5w@mail.gmail.com> (raw)
In-Reply-To: <519B9F74-17B7-407D-9DAD-E5A0C610108D@gmail.com>

On Thu, Jul 2, 2015 at 8:15 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> 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.

:) It is software GSO, and yes, given the 4.0 results for forwarding
on this platform, I would consider seriously cutting it down in size.
(say, 2 MTU, max, down from 64k, or less - should give better cache
behavior, too), That said, TSO/GSO/GRO is everywhere, and peeling,
needed. Take the intel ethernet chips, for starters.

But it would be best to experiment and benchmark, further.

>
>  - Jonathan Morton
>



-- 
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

      reply	other threads:[~2015-07-03 16:01 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 ` [Cerowrt-devel] [Cake] " Jonathan Morton
2015-07-03 16:01   ` Dave Taht [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/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=CAA93jw438n_efq+y-nSRz0+15Vx0e33PJ47DMOEXQ866rsww5w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@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