From: Sebastian Moeller <moeller0@gmx.de>
To: George Amanakis <gamanakis@gmail.com>
Cc: "Dave Täht" <dave.taht@gmail.com>,
"George Amanakis via Cake" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] new patchset for upstream net-next
Date: Mon, 27 Nov 2017 06:23:47 +0100 [thread overview]
Message-ID: <789EEFBB-F9ED-4D51-AE66-AD7AA6615562@gmx.de> (raw)
In-Reply-To: <732a82f3-133b-e27d-724c-ea3f91e77d81@gmail.com>
> On Nov 27, 2017, at 04:33, George Amanakis <gamanakis@gmail.com> wrote:
>
>
>> Whatever your primary use case is? My biggest concern is that it
>> simply not crash - 300 second long tests, 1200 seconds, all night
>> long over and over, again, pounding it flat.
>
> My home router runs x86_64 Archlinux on net-next with cake and nf_conntrack compiled as integrals. TSO, GSO and GRO are turned off. Up until now (24h) it has not crashed and everything seems stable. Dmesg does not report anything unusual. Ingress traffic is about 15 GiB, egress about 1 GiB.
>
> Cake configuration (Comcast cable, advertised 10Mbps/2Mbps):
> qdisc cake 8001: dev ens4 root refcnt 2 bandwidth 12200Kbit diffserv3 dual-dsthost wash ingress ack-filter rtt 100.0ms noatm overhead 18 via-ethernet mpu 64
> qdisc cake 8002: dev ens3 root refcnt 2 bandwidth 2500Kbit diffserv3 dual-srchost nat wash ack-filter rtt 100.0ms noatm overhead 18 via-ethernet mpu 64
Just like ECN ack-filter really only makes sense if the ACKs never hit the bottleneck link; I guess what I want to say, besides for testing, ack-filter on your ingress fro internet leg does not make too much sense...
Best Regards
>
> George
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2017-11-27 5:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 17:51 Dave Taht
[not found] ` <CACvFP_iRrHwYZmwMWt7o7wWxFkJqVnr54LSnykLU7AeHmvCa8g@mail.gmail.com>
[not found] ` <CACvFP_jTBczaZPvtGa9PRi5Fzg6CHD1MKcyMyXikPHY-06-jvg@mail.gmail.com>
[not found] ` <CAA93jw43TVJtQ75jANiHEPHFijPR8HMdwtQXcNoARcu7bj5OYg@mail.gmail.com>
[not found] ` <59515a10-e1c5-7b58-851f-ece09191fb43@gmail.com>
[not found] ` <CAA93jw6rCB+Ov51JQ=o4+KU4_pvQUharZzCVuWhzgHKuJNXCaw@mail.gmail.com>
2017-11-26 0:49 ` George Amanakis
2017-11-26 0:51 ` George Amanakis
2017-11-26 1:00 ` Dave Taht
2017-11-26 1:27 ` George Amanakis
2017-11-26 4:38 ` gamanakis
2017-11-26 5:46 ` Dave Taht
2017-11-26 8:15 ` Pete Heist
2017-11-27 3:33 ` George Amanakis
2017-11-27 5:08 ` Dave Taht
2017-11-27 5:23 ` Sebastian Moeller [this message]
[not found] ` <CACvFP_g+__PMu7KGuuR8oUb2z0gFTthEne9R17s2jQjE8MgF3Q@mail.gmail.com>
2017-11-27 14:28 ` [Cake] Fwd: " Georgios Amanakis
2017-11-26 2:27 ` [Cake] " gamanakis
2017-11-26 12:15 ` Toke Høiland-Jørgensen
2017-11-26 18:22 ` Dave Taht
2017-11-26 19:34 ` Toke Høiland-Jørgensen
2017-11-26 19:37 ` Kevin Darbyshire-Bryant
[not found] ` <CAJq5cE1NC9DS6hDRLYQZqiixbXgHuVZaAXH0wAOpjRS=A5aX6Q@mail.gmail.com>
2017-11-26 19:51 ` Jonathan Morton
2017-11-27 4:42 ` David Lang
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=789EEFBB-F9ED-4D51-AE66-AD7AA6615562@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=gamanakis@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