Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: George Amanakis <gamanakis@gmail.com>,
	George Amanakis via Cake <cake@lists.bufferbloat.net>
Subject: Re: [Cake] new patchset for upstream net-next
Date: Sun, 26 Nov 2017 09:15:54 +0100	[thread overview]
Message-ID: <5DA0BB5A-51F1-4478-9668-83B49E8C2252@gmail.com> (raw)
In-Reply-To: <CAA93jw67wz5r+4jdAQYp6MFN5gG8ryt+rgJ3_k0M8-CsQAjHZw@mail.gmail.com>

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


> On Nov 26, 2017, at 6:46 AM, Dave Taht <dave.taht@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.
> 
> rrul_be, rrul, 100 flows, 1000 flows, multiple stations, udp_flood,
> bittorrent, steam, with/without ack-filter, ack-filter-aggressive,
> asymmetric networks, as the default qdisc, unlimited, on mq
> hardware.... triple-isolate, dual-whatever, besteffort... ingress...
> every combination of keywords,
> 
> I lost track of the QA matrix once it started rivaling string theory
> in complexity.

I volunteer to cover the 'dual-whatever’ tests.

[-- Attachment #2: Type: text/html, Size: 8798 bytes --]

  reply	other threads:[~2017-11-26  8:15 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 [this message]
2017-11-27  3:33                       ` George Amanakis
2017-11-27  5:08                         ` Dave Taht
2017-11-27  5:23                         ` Sebastian Moeller
     [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=5DA0BB5A-51F1-4478-9668-83B49E8C2252@gmail.com \
    --to=peteheist@gmail.com \
    --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