All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TCP window based shaping
Date: Wed, 09 Feb 2005 22:38:20 +0000	[thread overview]
Message-ID: <420A90DC.6080108@dsl.pipex.com> (raw)
In-Reply-To: <42095013.8030600@wildgooses.com>

marco ghidinelli wrote:
> On Tue, Feb 08, 2005 at 11:49:39PM +0000, Ed Wildgoose wrote:
> 
>>Does anyone have any pointers on how other people have implemented tcp 
>>window adjustment to do bandwidth shaping?
>>
>>Granted the basic idea is to set the window size to be RTT * bandwidth, 
>>but a quick squiz at google turns up mostly papers on how to implement 
>>this at the sender end with a view to some new magic TCP 
>>implementation.  I'm really interested in notes on how to implement at 
>>the router side, perhaps with a view to writing a new QOS module.
>>
>>Biggest issue I can see right now is an architecture one, ie monitoring 
>>the incoming packet rate and then applying that to the outgoing ACK 
>>packets.
> 
> 
> instead of shaping the incoming traffic and estimate rate from the
> outgoing traffic, you can 'delay' the outgoing ACK, and estimate the rate
> from the raise of the sequence number.
> 
> so you just shape on the outgoing queue, without take care of the
> incoming traffic.
> 
> note that everything here is patented, so if you must have lawyers, if
> you want to develop..
> 
> :-/
> 
> http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2Fsearch-bool.html&r=0&f=S&lP&TERM1=packeteer&FIELD1=&co1=AND&TERM2=&FIELD2=&d=ptxt
> 

Ewwww thats not nice - not that I know what those would stop you being 
able to do.

I presume they just apply in the USA and wouldn't be enforcable in 
Europe yet as software patents are not allowed (yet)?

Andy.




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2005-02-09 22:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 23:49 [LARTC] TCP window based shaping Ed Wildgoose
2005-02-08 23:57 ` David Boreham
2005-02-09  1:59 ` Andy Furniss
2005-02-09 11:34 ` marco ghidinelli
2005-02-09 22:38 ` Andy Furniss [this message]
2005-02-11  2:57 ` Ed Wildgoose
2005-02-11 11:05 ` marco ghidinelli
2005-02-11 18:18 ` Ed Wildgoose
2005-02-11 23:45 ` Ed Wildgoose
2005-02-12  2:16 ` Andy Furniss
2005-02-12 13:19 ` Andy Furniss
2005-02-13  0:46 ` Ed Wildgoose
2005-02-14  0:27 ` marco ghidinelli
2005-02-14  0:38 ` marco ghidinelli
2005-02-15 22:33 ` Andy Furniss
2005-02-15 22:54 ` Andy Furniss
2005-02-16 14:52 ` Ed Wildgoose
2005-02-17  3:45 ` gypsy
2005-02-17 14:09 ` Ed Wildgoose
2005-03-12 10:10 ` Ow Mun Heng
2005-03-15 15:24 ` Ed Wildgoose
2005-03-16  7:46 ` Ow Mun Heng
2005-07-09  4:01 ` Don Cohen
2005-07-10 19:55 ` Andy Furniss
2005-07-12  1:50 ` TAKANO Ryousei
2005-07-12  8:46 ` Andy Furniss
2005-07-12 13:44 ` TAKANO Ryousei

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=420A90DC.6080108@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.