Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave@taht.net>
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cobalt through checkpatch
Date: Thu, 23 Nov 2017 17:44:54 +0000	[thread overview]
Message-ID: <5DCAAD9D-5DBF-475A-ACCF-84B8EEC66AE7@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <87po88x6sv.fsf@nemesis.taht.net>



> On 23 Nov 2017, at 17:07, Dave Taht <dave@taht.net> wrote:
> 
> Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
>> 
>> Just did a PR for turning max_skblen (or whatever it is) to a u32….since there *are* super packets out there >64KB.
> 
> There are?
There are!  Well there were.  For a brief time someone enable GRO on the ag71xx switch in LEDE and to my surprise all of a sudden I saw tc via cake reporting >1514 max packet sizes.  More of a surprise was seeing the number occasionally going backwards :-)
> 
>> Opinions on doing a PR for LEDE so they can enjoy(/crash) the fruits of our latest cobalt.  They’re currently missing ingress mode & ack filtering filtering toys.
> 
> Nah. Let's get it into net-next first this time. I would hope for some
> good comments.
Fair enough-ski - either call I was more than happy with.
> 
> Also, I *think* that that version will build on 4.9 without any backward
> compatability cruft except for patching pkt_sched.h. Is lede fully 4.9 now?
Sadly some targets are still 4.4.  It’s being worked on.

Enjoy your few days break!

Cheers,

Kevin


  reply	other threads:[~2017-11-23 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 21:59 Dave Taht
2017-11-23 15:14 ` Kevin Darbyshire-Bryant
2017-11-23 17:07   ` Dave Taht
2017-11-23 17:44     ` Kevin Darbyshire-Bryant [this message]
2017-11-23 21:34       ` 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=5DCAAD9D-5DBF-475A-ACCF-84B8EEC66AE7@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave@taht.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