From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC Advanced Limiting
Date: Mon, 17 Oct 2005 19:31:19 +0000 [thread overview]
Message-ID: <4353FC07.9000406@dsl.pipex.com> (raw)
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB04B52C@xavier.staff.greatlakes.net>
Eliot, Wireless and Server Administrator, Great Lakes Internet wrote:
> Thank you for your response.
>
> I do know how to shape a specific direction of traffic. Given that I am the ISP sitting between the customer and the Internet, it is trivial for me to shape both directions.
>
I think the point Jason was making is that you are shaping from the
wrong end of the bottleneck if you shape traffic from your customers.
If their link speed to you is high and you shape to well below it then
it won't be too bad, but the point stands that it is not the same as
when shaping from the "right" end of the bottleneck, especially WRT
latency and jitter.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-17 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 14:41 [LARTC] HFSC Advanced Limiting Eliot, Wireless and Server Administrator, Great Lakes Internet
2005-10-13 19:45 ` Jason Boxman
2005-10-13 20:24 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2005-10-13 20:57 ` Tomasz Chilinski
2005-10-14 12:53 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2005-10-14 13:07 ` Nickola Kolev
2005-10-14 13:12 ` Tomasz Chilinski
2005-10-14 13:14 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2005-10-14 16:18 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2005-10-17 19:31 ` Andy Furniss [this message]
2005-10-19 10:49 ` Andy Furniss
2005-10-19 10:55 ` Andy Furniss
2005-10-20 12:54 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
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=4353FC07.9000406@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.