Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: "Jonas Mårtensson" <martensson.jonas@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Testing variants of the MTU latency scaling
Date: Tue, 24 Apr 2018 19:22:28 +0000	[thread overview]
Message-ID: <B1CD80ED-4FD0-4721-930D-92AE2EAD13AB@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAM9iV=+RfjRYCm3SnDyHovjbNTbbBcNpOvJNVA_+rNXbaO6_gA@mail.gmail.com>

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

Assuming you’re using luci to configure then enabling both show and use advanced configuration & show and use dangerous configurations… then enter ‘ingress’ in the ‘advanced option string to pass to ingress queuing’ will enable ingress mode.

Maybe that helps?

> On 24 Apr 2018, at 20:04, Jonas Mårtensson <martensson.jonas@gmail.com> wrote:
> 
> 
> 
> On Tue, Apr 24, 2018 at 1:45 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Jonas Mårtensson <martensson.jonas@gmail.com> writes:
> 
> > One thing that is still not clear to me from these results: if I run
> > cake on an IFB without ingress mode (i.e. the default?), does the MTU
> > scaling have any impact on TCP download throughput?
> 
> Odds are that not using ingress mode will make Cake lose control of the
> bottleneck (that is what happened when I tried running a quick test),
> and so will mess up both latency and throughput as you hit the bloated
> upstream link buffer...
> 
> So using cake through sqm-scripts in OpenWRT/LEDE for ingress shaping does not currently work very well then? I guess the sqm-scripts should be updated to actually use ingress mode at some point...
> 
> /Jonas
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


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-04-24 19:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-22 20:46 Toke Høiland-Jørgensen
2018-04-22 21:09 ` Jonathan Morton
2018-04-22 21:31   ` Toke Høiland-Jørgensen
2018-04-23 11:23   ` Jonas Mårtensson
2018-04-24 11:45     ` Toke Høiland-Jørgensen
2018-04-24 19:04       ` Jonas Mårtensson
2018-04-24 19:22         ` Kevin Darbyshire-Bryant [this message]
2018-04-24 20:27           ` Jonas Mårtensson
2018-04-24 21:11             ` Sebastian Moeller
2018-04-23  9:52 ` Jonathan Morton
2018-04-23 10:13   ` Toke Høiland-Jørgensen
2018-04-23 10:50     ` Jonathan Morton
2018-04-24  8:11       ` Kevin Darbyshire-Bryant
2018-04-24  8:14         ` Jonathan Morton
2018-04-24  8:29           ` 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=B1CD80ED-4FD0-4721-930D-92AE2EAD13AB@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    --cc=martensson.jonas@gmail.com \
    --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