From: Flemming Frandsen <ff@nrvissing.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] even bandwith for users on 2 newtworks
Date: Mon, 16 Jan 2006 21:25:51 +0000 [thread overview]
Message-ID: <43CC0F5F.2050301@nrvissing.net> (raw)
In-Reply-To: <43cab7ca69c72@wp.pl>
Alexey Toptygin wrote:
> No, attaching to the input is just as easy as to the output. The reason
> that isn't implemented is that it wouldn't really be useful.
You are full of it.
What everybody who asks for shaping want is mainly ingress shaping and
it works just fine.
When TCP starts to notice that packets are getting lost it will throttle
down and transmit slower, just like any non-idiotic protocol, because
that's the way the Internet works.
You are right that the packets that have already traversed the DSL line
have consumed bandwidth that can never be reclaimed, but the point is
that once you start dropping packets then fewer will follow and the
situation will stabilize.
The fact remains that ingress shaping is immensely useful and that it works.
Linux traffic shaping doesn't support it out of the box (pre 2.6.16) and
that's because it was hard(er) to implement, not because it's not useful
it is in the real world.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-01-16 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 20:59 [LARTC] even bandwith for users on 2 newtworks Hariett Jones
2006-01-15 21:42 ` Flemming Frandsen
2006-01-15 23:25 ` Carl-Daniel Hailfinger
2006-01-16 11:45 ` Flemming Frandsen
2006-01-16 13:01 ` Alexey Toptygin
2006-01-16 21:25 ` Flemming Frandsen [this message]
2006-01-16 21:41 ` Peter Surda
2006-01-17 0:06 ` Carl-Daniel Hailfinger
2006-01-17 13:27 ` Flemming Frandsen
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=43CC0F5F.2050301@nrvissing.net \
--to=ff@nrvissing.net \
--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.