From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Is ingress QoS worth the pain?
Date: Tue, 2 Jun 2015 21:47:58 -0700 [thread overview]
Message-ID: <CAA93jw4H4fuDm2WLMGnmdBpu2LsyTy0nzyQPCAfHjEtB3TdmYQ@mail.gmail.com> (raw)
In-Reply-To: <5566BD00.2010205@openwrt.org>
Please note our mail server is failing and I am pulling together the
resources and time to replace it. (if anyone has a good antispam setup
and some time, that would be nice)
It is sorting through an enormous backlog now.
On Thu, May 28, 2015 at 12:00 AM, Steven Barth <cyrus@openwrt.org> wrote:
> Hi everyone,
>
> again a bit of a basic question, but what are the advantages of doing
> ingress shaping in SQM?
>
> To me it wastes a lot of CPU cycles (decreases forwarding performance)
> and you can't really "unsend" any packets from the ISP. What I mean is
> in 99% of cases your internal forwarding capacity is usually (much?)
> bigger than what the ISP sends to at any rate.
Do you want hundreds of ms, or even seconds, induced latency on your
link because your ISP massively overbuffers at their end on their
shaper?
"Here ya go! 100Mbits of bandwidth... but when you use it, stop
playing your game, 'cause you are going to get fragged!"
http://burntchrome.blogspot.com/2014/05/disabling-shaping-in-one-direction-with.html
> What do I miss here? Some effects on TCP rate-limiting?
yep.
The ideal answer is for the ISP gear to have a shaper that works well
at all speeds for their customers.
>
>
> Cheers,
>
> Steven
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next prev parent reply other threads:[~2015-06-03 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 7:00 Steven Barth
2015-06-03 4:47 ` Dave Taht [this message]
2015-06-03 10:04 ` Kevin Darbyshire-Bryant
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=CAA93jw4H4fuDm2WLMGnmdBpu2LsyTy0nzyQPCAfHjEtB3TdmYQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cyrus@openwrt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox