From: Hal Murray <hmurray@megapathdsl.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Hal Murray <hmurray@megapathdsl.net>,
cerowrt-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] any fedora 22 users out there?
Date: Tue, 02 Jun 2015 22:43:52 -0700 [thread overview]
Message-ID: <20150603054352.B476D406061@ip-64-139-1-69.sjc.megapath.net> (raw)
Dave Taht said:
> what does
> tc qdisc show
> say?
[murray@fed ~]$ tc qdisc show
qdisc mq 0: dev eth0 root
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514
target 5.0ms interval 100.0ms ecn
[murray@fed ~]$
For reference, here is Fedora 21:
[murray@glypnod ~]$ tc qdisc show
qdisc mq 0: dev eth0 root
qdisc pfifo_fast 0: dev eth0 parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
[murray@glypnod ~]$
--
These are my opinions. I hate spam.
next reply other threads:[~2015-06-03 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 5:43 Hal Murray [this message]
2015-06-03 5:48 ` Dave Taht
-- strict thread matches above, loose matches on Subject: below --
2015-05-26 19:14 Dave Taht
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=20150603054352.B476D406061@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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