From: Michal Soltys <soltys@ziu.info>
To: lartc@vger.kernel.org
Subject: Re: HFSC not working as expected
Date: Mon, 07 Jul 2014 10:08:43 +0000 [thread overview]
Message-ID: <53BA71AB.3080003@ziu.info> (raw)
In-Reply-To: <53AC30A8.2080403@yescomputersolutions.com>
On 2014-07-06 18:42, Andy Furniss wrote:
> Alan Goodman wrote:
>
>> I added 'stab overhead 40 linklayer atm' to my root qdisc line since
>> I am confident my connection uses LLC multiplexing. This transformed
>> the hfsc based shaper to being the most accurate I have so far
>> experienced. I am able to set tc upload limit by the sync speed, and
>> tc downstream by the sync minus 12% which accounts for some rate
>> limiting BT do on all lines (they limit downstream to 88.2% of sync
>> rate).
>
> If you have the choice of pppoa vs pppoe why not use a so you can use
> overhead 10 and be more efficient for upload.
>
For the record - choosing PPPoE usually allows switching [very cheap]
adsl routers into bridge mode - avoiding their connection tracking
limits altogether (great for torrents) and getting public ip on linux
machine easily.
next prev parent reply other threads:[~2014-07-07 10:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 14:39 HFSC not working as expected Alan Goodman
2014-07-01 12:25 ` Michal Soltys
2014-07-01 13:19 ` Alan Goodman
2014-07-01 13:30 ` Michal Soltys
2014-07-01 14:33 ` Alan Goodman
2014-07-03 0:12 ` Michal Soltys
2014-07-03 0:56 ` Alan Goodman
2014-07-06 1:18 ` Michal Soltys
2014-07-06 15:34 ` Alan Goodman
2014-07-06 16:42 ` Andy Furniss
2014-07-06 16:49 ` Andy Furniss
2014-07-06 16:49 ` Alan Goodman
2014-07-06 16:54 ` Alan Goodman
2014-07-06 20:42 ` Andy Furniss
2014-07-06 22:18 ` Alan Goodman
2014-07-06 22:24 ` Andy Furniss
2014-07-07 0:01 ` Alan Goodman
2014-07-07 9:54 ` Michal Soltys
2014-07-07 9:58 ` Michal Soltys
2014-07-07 10:08 ` Michal Soltys [this message]
2014-07-07 10:10 ` Michal Soltys
2014-07-07 10:59 ` Alan Goodman
2014-07-07 15:38 ` Alan Goodman
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=53BA71AB.3080003@ziu.info \
--to=soltys@ziu.info \
--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.