From: Stephen Hemminger <shemminger@vyatta.com>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: Stephen Hemminger <stephen.hemminger@vyatta.com>,
netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH 0/7] Final ADSL-optimizer patch series
Date: Thu, 17 Apr 2008 10:10:30 -0700 [thread overview]
Message-ID: <20080417101030.6807d577@extreme> (raw)
In-Reply-To: <Pine.LNX.4.64.0804092249550.21022@ask.diku.dk>
On Wed, 9 Apr 2008 22:57:25 +0200 (CEST)
Jesper Dangaard Brouer <hawk@diku.dk> wrote:
>
> This is the final part of the ADSL-optimizer patch, which is the real
> "holy grail" of packet scheduling on ADSL/ATM lines. (Referring to
> Wondershaper claim of the "holy grail".)
>
> Shaping on ADSL has always been surrounded with mystique. People
> reduce and tweek the upstream bandwidth, but how much and why does it
> not work all the time? With this change, the tweeking and bandwidth
> waste is gone, simply specify the bandwidth you bought.
>
> This patch series introduces a parameter called "linklayer", which
> currently supports "ethernet" and "atm". Simply, what happens is,
> that the rate table is aligned for ATM cells.
>
> This is a general implementation for all shapers, except HFSC which
> does not use rate table lookups. Earlier (around Sep.2007), Patrick
> McHardy wanted to make an even more general patch, that also included
> HFSC. Nothing has happened since...
>
> After talking with DaveM (at his house during an icehocky match), I've
> come to the conclusion that we have something that works now (and has
> been since Oct.2004) and we should use it! Everybody is allowed to
> change and improve upon that. Its should not mean that we keep
> something like this back, which will allow packet scheduling to
> actually work on ADSL. One should also realize that different shapers
> have different properties.
>
> Patrick's further improvements can use the same userspace parameter
> "linklayer" to allow userspace parameter compatibility.
>
> This patch series is ABI (Application Binary Interface) compatible.
>
> See you around,
> Jesper Brouer
Applied but:
* Used constants from atm.h, pulled in include/linux/atm.h etc.
* rolled 2-7 together in one patch. All though small patches are preferred
it is more important that the build doesn't break after each patch so
if an API changes (in this case calc_rtable) fix all the functions that
use it in one patch.
* Some mailer damage, so the patches would not apply automatically, had
to do hand edits.
prev parent reply other threads:[~2008-04-17 17:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 20:57 [PATCH 0/7] Final ADSL-optimizer patch series Jesper Dangaard Brouer
2008-04-09 20:59 ` [PATCH 1/7] In police, fix uninitialized "overhead" variable Jesper Dangaard Brouer
2008-04-09 21:01 ` [PATCH 2/7] ATM cell alignment Jesper Dangaard Brouer
2008-04-10 14:35 ` Chas Williams (CONTRACTOR)
2008-04-11 4:53 ` Jesper Dangaard Brouer
2008-04-11 14:18 ` Chas Williams (CONTRACTOR)
2008-04-11 12:51 ` Patrick McHardy
2008-04-11 17:35 ` Jesper Dangaard Brouer
2008-04-13 4:44 ` Patrick McHardy
2008-04-13 11:24 ` Andy Furniss
2008-04-14 5:59 ` Jesper Dangaard Brouer
2008-04-15 23:41 ` Andy Furniss
2008-04-09 21:02 ` [PATCH 3/7] Parsing linklayer types Jesper Dangaard Brouer
2008-04-09 21:03 ` [PATCH 4/7] Add linklayer parameter to filter action police Jesper Dangaard Brouer
2008-04-09 21:04 ` [PATCH 5/7] Add linklayer parameter to CBQ Jesper Dangaard Brouer
2008-04-09 21:06 ` [PATCH 6/7] Add linklayer parameter to HTB Jesper Dangaard Brouer
2008-04-09 21:07 ` [PATCH 7/7] Add linklayer parameter to TBF Jesper Dangaard Brouer
2008-04-14 5:40 ` [PATCH 0/7] Final ADSL-optimizer patch series David Miller
2008-04-17 17:10 ` Stephen Hemminger [this message]
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=20080417101030.6807d577@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=hawk@diku.dk \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=stephen.hemminger@vyatta.com \
/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;
as well as URLs for NNTP newsgroup(s).