Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Backporting 'tc class' support
Date: Sun, 15 Jul 2018 00:48:46 +0000	[thread overview]
Message-ID: <4C12C6A1-84E3-4B78-885F-F5C212CD13FF@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <8736wla3lq.fsf@toke.dk>


[-- Attachment #1.1: Type: text/plain, Size: 576 bytes --]



> On 14 Jul 2018, at 22:50, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> Now that CAKE has been accepted upstream, I figured it was a good time
> to backport the 'tc class' support. So I did, back to kernel v4.9.
> 
> This is in the master branch; anyone feel like testing? With this, the
> version of CAKE in the master branch should be identical to the version
> that will be in Linux 4.19 :)

I need the attached patch to get it to build on openwrt - it looks like an include guard order thing.

Though it builds, not yet run in any way ;-)

KDB


[-- Attachment #1.2: 0001-Fix-build-on-Openwrt.patch --]
[-- Type: application/octet-stream, Size: 793 bytes --]

From ad2063e926d57f1a0f4cae8d1fdb3ba7ede6ec23 Mon Sep 17 00:00:00 2001
From: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Date: Sun, 15 Jul 2018 01:17:18 +0100
Subject: [PATCH] Fix build on Openwrt

Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
---
 sch_cake.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sch_cake.c b/sch_cake.c
index dfc967e..012af95 100644
--- a/sch_cake.c
+++ b/sch_cake.c
@@ -65,8 +65,8 @@
 #include <linux/reciprocal_div.h>
 #include <net/netlink.h>
 #include <linux/version.h>
-#include <linux/if_vlan.h>
 #include "pkt_sched.h"
+#include <linux/if_vlan.h>
 #include <net/pkt_cls.h>
 #include <net/tcp.h>
 #if LINUX_VERSION_CODE < KERNEL_VERSION(4, 2, 0)
-- 
2.15.2 (Apple Git-101.1)


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

  reply	other threads:[~2018-07-15  0:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14 21:50 Toke Høiland-Jørgensen
2018-07-15  0:48 ` Kevin Darbyshire-Bryant [this message]
2018-07-15  9:48   ` Toke Høiland-Jørgensen
2018-07-15 20:13     ` Kevin Darbyshire-Bryant
2018-07-15 20:23       ` Toke Høiland-Jørgensen
2018-07-15 22:41         ` Kevin Darbyshire-Bryant
2018-07-16  2:09           ` Jonathan Morton
2018-07-16  4:00             ` Dave Taht
2018-07-16  9:24               ` Toke Høiland-Jørgensen
2018-07-16  9:30             ` Toke Høiland-Jørgensen
2018-07-16  9:57               ` Jonathan Morton
2018-07-16 10:18                 ` Toke Høiland-Jørgensen
2018-07-16 12:06                   ` Georgios Amanakis
2018-07-16 12:28                     ` Toke Høiland-Jørgensen
2018-07-16 12:44                       ` Kevin Darbyshire-Bryant

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=4C12C6A1-84E3-4B78-885F-F5C212CD13FF@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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