From: moeller0 <moeller0@gmx.de>
To: "techicist@gmail.com" <techicist@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Configuring cake for VDSL2 bridged connection
Date: Fri, 26 Aug 2016 13:29:55 +0200 [thread overview]
Message-ID: <23996FEA-F20C-4654-9A57-792927BCDC83@gmx.de> (raw)
In-Reply-To: <CANiaOCk4VF8Nhs_+6uK-QBWXe9WWTQecpWB65SZ+D044BGg7aw@mail.gmail.com>
Hi techicist,
> On Aug 26, 2016, at 13:15 , techicist@gmail.com wrote:
>
> Is flowblind likely to give better performance?
That depends on your definition of better, I guess. Typically flow-fair queuing seems to be what most people prefer (unless an application either does not respond to AQM signals or open an excessive amount of individual flows flow-fair queueing effectively treats most traffic sources equal, pretty much what people seem to want, add to this a bit of classification to exempt e.g. VOIP traffic from only getting its flow-fair share of the bandwidth and the whole thing also works reasonably well with slow links). People suffering from unruly applications (like mis-configured? bit-torrent clients or recently windows update) often ask for per-application fairness, but that is not something a router will ever be able to deliver in my opinion; the closest we get to this would be fairnes by internal or external end-IP addresses. Luckily cake offers just these modes “dsthost”, “srchost” and even better offers a combination modes that will on a first level attempt per host-IP fairness and within each host IP also per-flow fairness (“dual-srchost” and “dual-dsthost”, and even “triple-isolate” which systematically might be better called “dual-srchost-dsthost” since it offers fist level fairness based on an under-documented mix of src and dst addresses, but I digress). Please note that on a typical homerouter, due to NAT, all the IP addressed based fairness modes will not work for IPv4 on the wan interface, IPv6 traffic should be fine, but IPv4 basically degrades into a computationally more intensive version of flow-fairness (as after NAT cake only sees the routers external IP for all internal hosts). This might have been more than you wanted to know…
Best Regards
Sebastian
>
> netperfrunner looks very useful. Thank you for that.
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2016-08-26 11:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 13:44 techicist
2016-08-23 14:27 ` moeller0
2016-08-23 15:13 ` techicist
2016-08-23 20:09 ` Sebastian Moeller
2016-08-24 17:01 ` techicist
2016-08-24 17:03 ` techicist
2016-08-24 17:03 ` techicist
2016-08-24 17:16 ` Alan Jenkins
2016-08-24 19:33 ` techicist
2016-08-24 19:47 ` Alan Jenkins
2016-08-24 19:49 ` Alan Jenkins
2016-08-25 14:53 ` techicist
2016-08-26 8:14 ` Alan Jenkins
2016-08-26 11:15 ` techicist
2016-08-26 11:29 ` moeller0 [this message]
2016-08-26 11:32 ` techicist
2016-08-27 7:43 ` Alan Jenkins
2016-08-27 16:17 ` techicist
2016-08-27 17:48 ` Alan Jenkins
2016-09-14 20:06 ` techicist
2016-09-14 20:41 ` Kevin Darbyshire-Bryant
2016-09-14 20:48 ` Sebastian Moeller
2016-09-15 9:24 ` Kevin Darbyshire-Bryant
2016-09-15 9:43 ` techicist
2016-08-26 11:52 ` Alan Jenkins
2016-08-26 12:04 ` techicist
2016-08-27 7:31 ` Alan Jenkins
2016-08-24 8:52 ` 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=23996FEA-F20C-4654-9A57-792927BCDC83@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=techicist@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