Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Cake List <cake@lists.bufferbloat.net>
Subject: Cake on openwrt - falling behind
Date: Sat, 30 Jun 2018 08:29:05 +0000	[thread overview]
Message-ID: <76AFB043-484D-4307-88B3-08ED8B9E3809@darbyshire-bryant.me.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

Hi Chaps,

I’m concerned that cake on openwrt is falling behind.  Due to strange behaviour at least on MIPS since commit https://github.com/dtaht/sch_cake/commit/af1d7cde7046af55ec867b29854d754816b64bc8 Switch rates to 64bit, openwrt has been ‘stuck’ on the prior commit.  I personally have hack patches in my that effectively reverts the conversion to 64 netlink values in cake & tc and I’m pleased to say that works, however the wider community are a) not so lucky b) not actually running our latest code, there are a number of tweaks to the ack filter code that openwrt users are not benefitting from.

Toke & myself dug into this a bit and we don’t, so far, think this is a bug in cake but is rather exposing an issue in netlink handling.  But we’ve hit an information vacuum, in essence I’m only seeing this on MIPS/Openwrt *BUT* that’s the only thing I can actually test on.  So is this 32bit MIPS only?  Is it Openwrt only?  Is it MIPS & Openwrt only?  Is it 32bit archs only?  And so on.

This really needs to be investigated & solved, so that a) openwrt’s cake can be bumped and b) Someone can get on with backporting the class handling code (which is being sent upstream) to 4.14/4.9 (maybe earlier)

If *you* have the means of compiling the latest cake & tc code on your platform could you please do so and report architecture etc if you do/do not see cake’s tin stats from ‘tc -s qdisc’ (that’s the biggest indicator of the issue)


Cheers,

Kevin D-B

012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2018-06-30  8:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=76AFB043-484D-4307-88B3-08ED8B9E3809@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --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