All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Russell Stuart <russell-tcatm@stuart.id.au>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
	Patrick McHardy <kaber@trash.net>,
	Jesper Dangaard Brouer <hawk@diku.dk>
Subject: Re: [PATCH REPOST 1/2] NET: Accurate packet scheduling for ATM/ADSL (kernel)
Date: Tue, 17 Oct 2006 09:07:24 -0400	[thread overview]
Message-ID: <1161090444.5555.13.camel@jzny2> (raw)
In-Reply-To: <1161041677.6247.1.camel@ras.pc.brisbane.lube>

On Tue, 2006-17-10 at 09:34 +1000, Russell Stuart wrote:
> The Linux traffic's control engine inaccurately calculates
> transmission times for packets sent over ADSL links.  For
> some packet sizes the error rises to over 50%.  This occurs
> because ADSL uses ATM as its link layer transport, and ATM
> transmits packets in fixed sized 53 byte cells.
> 
> This changes the kernel rate table lookup, to be able to lookup
> packet transmission times over all ATM links, including ADSL,
> with perfect accuracy. The accuracy is dependent on the rate
> table that is calculated in userspace by iproute2 command tc.
> 
> A longer presentation of the patch, its rational, what it
> does and how to use it can be found here:
>    http://www.stuart.id.au/russell/files/tc/tc-atm/
> 
> A earlier version of the patch, and a _detailed_ empirical
> investigation of its effects can be found here:
>    http://www.adsl-optimizer.dk/
> 
> Signed-off-by: Jesper Dangaard Brouer <hawk@comx.dk>
> Signed-off-by: Russell Stuart <russell-tcatm@stuart.id.au>

ACKed-by: Jamal Hadi Salim

When Patrick has his patch ready after this goes in we can revisit.

cheers,
jamal


  reply	other threads:[~2006-10-17 13:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 23:34 [PATCH REPOST 1/2] NET: Accurate packet scheduling for ATM/ADSL (kernel) Russell Stuart
2006-10-17 13:07 ` jamal [this message]
2006-10-19  3:41   ` David Miller
2006-10-19 14:38   ` Patrick McHardy
2006-10-20  0:49     ` jamal
2006-10-20  8:54       ` Patrick McHardy
2006-10-23 11:22     ` Russell Stuart
2006-10-23 12:39       ` Patrick McHardy
2006-10-23 21:54         ` Russell Stuart
2006-10-24 16:19           ` Patrick McHardy
2006-10-24 20:00             ` Jesper Dangaard Brouer
2006-10-24 23:46             ` Russell Stuart
2006-11-30 13:07               ` Patrick McHardy
2007-01-17 23:07                 ` Russell Stuart
2007-01-18  4:05                   ` Patrick McHardy
2007-01-18  6:16                     ` Russell Stuart
     [not found]                       ` <45AF5C02.1010005@trash.net>
2007-01-19  3:11                         ` Russell Stuart
2007-01-19 12:19                           ` Patrick McHardy
2007-01-20  3:25                             ` Russell Stuart
2007-01-20  8:47                               ` Patrick McHardy
2007-01-21  7:45                                 ` Russell Stuart
2007-01-24 16:38                                   ` Patrick McHardy
2007-01-24 22:32                                     ` Russell Stuart
2007-01-25  0:06                                       ` Patrick McHardy
2007-01-25  0:55                                         ` Russell Stuart

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=1161090444.5555.13.camel@jzny2 \
    --to=hadi@cyberus.ca \
    --cc=davem@davemloft.net \
    --cc=hawk@diku.dk \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=russell-tcatm@stuart.id.au \
    /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.