From: "Hoggins!" <fuckspam@wheres5.com>
To: lartc@vger.kernel.org
Subject: Re: Weird traffic shaping behavior after kernel upgrade
Date: Mon, 06 Jan 2014 14:04:13 +0000 [thread overview]
Message-ID: <52CAB7DD.4080907@wheres5.com> (raw)
In-Reply-To: <52C9E5FB.8070502@wheres5.com>
Hello Dave,
I'll have to try that.
But for the moment, I found a "solution", expecting to use something
"cleaner" : I downgraded to kernel 3.10.25, and everything is working as
usual.
The machine is a production server for a little student radio in France,
so I cannot test a lot without shutting down the entire station.
The downgrade did the trick, so the problem is kinda "solved" for me
(although having the latest kernel would have been a better solution for
me I guess). Anyway, I'm going to tune these policies a bit, as you are
suggesting.
As for the reason I'm not running sfq on all qdiscs, well... as you
understand, with my very poor knowledge, I've been working on this
little script for a long time to have an acceptable level of service. I
had finally found the "perfect" match for the desired performances, and
the results of my "researches" showed that I had to use sfq only on the
qdiscs that did not require a "guaranteed" (although this is not
entirely correct, as we are working on a ADSL connection) throughput :
the classes having sfq are used for TCP operations such as web surfing,
and the returning of ACK packets for example. The other ones have fixed
limited bandwidth (not borrowable) for UDP (RTP) streams directly to
broadcast servers.
Thanks for your help, I'll get back on this list soon.
Hoggins!
Le 06/01/2014 00:41, Dave Taht a écrit :
> Is there some reason you aren't running sfq on all qdiscs? That could
> be a cause.
>
> and:
>
> try
>
> fq_codel target 20ms quantum 300 limit 600
>
> instead of sfq.
next prev parent reply other threads:[~2014-01-06 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 23:08 Weird traffic shaping behavior after kernel upgrade Hoggins!
2014-01-06 1:50 ` Remy Mudingay
2014-01-06 8:59 ` Hoggins!
2014-01-06 11:18 ` Remy Mudingay
2014-01-06 14:04 ` Hoggins! [this message]
2014-01-06 14:05 ` Hoggins!
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CAB7DD.4080907@wheres5.com \
--to=fuckspam@wheres5.com \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.