From: Michael Richardson <mcr@sandelman.ca>
To: Richard Smith <smithbone@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Problems testing sqm
Date: Fri, 23 Oct 2015 14:41:28 -0400 [thread overview]
Message-ID: <12883.1445625688@sandelman.ca> (raw)
In-Reply-To: <562A5BE5.6010101@gmail.com>
Richard Smith <smithbone@gmail.com> wrote:
> My test setup:
> Laptop<--1000BaseT-->DUT<--1000baseT-->Server
So, given that the DUT is the only real constraint in the network, what
do you expect to see from this setup?
Given that the probably DUT can't forward at Gb/s, and it certainly can't
shape anything, it's gonna drop packets, and it's probably gonna drop them in
Rx, having overrun the Rx-queue (so tail-drop). If there is too much ram
(bufferbloated), then you'll see different results...
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2015-10-23 18:41 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 16:10 Richard Smith
2015-10-23 16:13 ` Dave Taht
2015-10-23 16:21 ` Rich Brown
2015-10-23 16:45 ` Richard Smith
2015-10-23 16:43 ` Richard Smith
2015-10-23 17:42 ` Sebastian Moeller
2015-10-23 17:15 ` David Lang
2015-10-23 17:02 ` Alan Jenkins
2015-10-23 17:30 ` Richard Smith
2015-10-23 17:50 ` Sebastian Moeller
2015-10-23 17:45 ` Sebastian Moeller
2015-10-23 17:22 ` Aaron Wood
2015-10-23 17:47 ` Sebastian Moeller
2015-10-23 17:48 ` Richard Smith
2015-10-23 17:57 ` David Lang
2015-10-23 19:08 ` Sebastian Moeller
2015-10-23 17:38 ` Sebastian Moeller
2015-10-23 18:05 ` Richard Smith
2015-10-23 18:41 ` Michael Richardson [this message]
2015-10-23 20:18 ` Richard Smith
2015-10-23 22:48 ` David P. Reed
2015-10-24 7:59 ` Sebastian Moeller
2015-10-23 22:51 ` Aaron Wood
2015-10-23 22:53 ` David P. Reed
2015-10-24 8:07 ` Sebastian Moeller
2015-10-24 16:34 ` David P. Reed
2015-10-24 16:52 ` Jonathan Morton
2015-10-24 18:58 ` David P. Reed
2015-10-25 23:21 ` David Lang
2015-10-26 9:53 ` Jonathan Morton
2015-10-24 17:24 ` Sebastian Moeller
2015-10-24 17:30 ` Aaron Wood
2015-10-24 10:20 ` Dave Taht
2015-10-24 17:21 ` Sebastian Moeller
2015-10-25 15:10 ` Richard Smith
2015-10-25 16:07 ` [Cerowrt-devel] Problems testing sqm (solved) Richard Smith
2015-10-25 17:36 ` Rich Brown
2015-10-25 20:02 ` Richard Smith
2015-10-25 20:33 ` Sebastian Moeller
2015-10-25 20:44 ` Richard Smith
2015-10-26 11:17 ` Toke Høiland-Jørgensen
2015-10-26 12:35 ` Richard Smith
2015-10-26 11:50 ` Dave Taht
2015-10-26 12:27 ` Richard Smith
2015-10-26 13:41 ` Sebastian Moeller
2015-10-26 13:48 ` Dave Taht
2015-10-26 18:15 ` David Lang
2015-10-26 18:26 ` Sebastian Moeller
2015-10-26 18:31 ` David Lang
2015-10-26 21:01 ` Richard Smith
2015-10-26 22:23 ` Richard Smith
2015-10-26 13:50 ` [Cerowrt-devel] ***UNCHECKED*** " Toke Høiland-Jørgensen
2015-10-26 14:30 ` Sebastian Moeller
2015-10-26 21:54 ` Richard Smith
2015-10-26 22:04 ` Richard Smith
2015-10-25 20:07 ` [Cerowrt-devel] " Sebastian Moeller
2015-10-25 21:50 ` Jonathan Morton
2015-10-25 22:44 ` Richard Smith
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12883.1445625688@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=smithbone@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