Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Georgios Amanakis <g_amanakis@yahoo.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] WAN ingress rate with concurrent downloads
Date: Sun, 30 Oct 2016 12:43:11 -0400	[thread overview]
Message-ID: <1477845791.1404.2.camel@yahoo.com> (raw)
In-Reply-To: <mailman.1.1477670401.20617.cake@lists.bufferbloat.net>

Dear All,

I think Sebastian's theory has a weak point. 

> Again I believe you just show bit-torrent misbehaving ...

I can easily reproduce this behaviour if one LAN-host downloads
multiple files using TCP (e.g. 2 or more kernels simultaneously from ht
tp://www.kernel.org). 

> For me this looks like bwmon accounts the incoming packets before
> cake sees and drops them ...

If only one download takes place then the bandwidth bmon reports on
WAN-ingress is the same as the limit set in cake. I don't think that
bmon accounts the incoming packets before cake sees them. Furthermore,
Wireshark reports that all bittorrent traffic in my case are TCP
packets, and reports the same bandwidth usage as bmon on WAN-ingress. 

The only way I have found that WAN-ingress limit is obeyed, is using
act_police with the in-kernel bandwidth estimator (i.e. tc filter add
dev enp0s13 parent ffff: protocol all estimator 10msec 80msec u32 match
u32 0 0 police avrate 3300kbit drop flowid :1). But then there is an
discrepancy between WAN-ingress and LAN-egress (i.e. WAN-ingress is at
~400kbytes/s and LAN-egress on the host running bittorrent is
~220kbytes/s). Unfortunately I cannot see the bandwidth my cable-modem
syncs at (I searched the web-interface but did not find it; it is a
Comcast-provided Arris TG1682G).

Noah, could you try and see what happens if instead of bittorrent a
LAN-host downloads multiple files using TCP?

Thank you all for your feedback,
George

       reply	other threads:[~2016-10-30 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1477670401.20617.cake@lists.bufferbloat.net>
2016-10-30 16:43 ` Georgios Amanakis [this message]
2016-10-30 19:27   ` Sebastian Moeller
     [not found] <1462124589.1190968.1481310707746.ref@mail.yahoo.com>
2016-12-09 19:11 ` George Amanakis
2016-12-10 19:33   ` Benjamin Cronce
     [not found] <mailman.5.1477497601.28053.cake@lists.bufferbloat.net>
2016-10-27  0:10 ` G. Amanakis
2016-10-27  0:16   ` G. Amanakis
2016-10-27  6:41     ` Sebastian Moeller
2016-10-27 16:42       ` Noah Causin
2016-10-28  1:34     ` Georgios Amanakis
2016-10-28  7:45       ` Sebastian Moeller

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=1477845791.1404.2.camel@yahoo.com \
    --to=g_amanakis@yahoo.com \
    --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