From: Michael Richardson <mcr@sandelman.ca>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
Cc: "Bloat@lists.bufferbloat.net" <Bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] recommended PC config for network testing using Ubuntu
Date: Mon, 23 Feb 2015 17:03:14 -0500 [thread overview]
Message-ID: <604.1424728994@sandelman.ca> (raw)
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE931947C9E@xmb-aln-x05.cisco.com>
What Jonathan said:
- it's not your hardware, it's your kernel configuration.
You could install a distro with a newer kernel, but that won't actually solve
the problem since nobody is shipping 3.19 yet, and I think you want the
latest code so that you can have the latest AQM.
--
] 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 [
prev parent reply other threads:[~2015-02-23 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 15:14 Bill Ver Steeg (versteb)
2015-02-23 16:51 ` Jonathan Morton
2015-02-23 22:18 ` Bill Ver Steeg (versteb)
2015-02-23 18:31 ` Dave Taht
2015-02-23 19:03 ` Dave Taht
2015-02-23 22:03 ` Michael Richardson [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=604.1424728994@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=Bloat@lists.bufferbloat.net \
--cc=versteb@cisco.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