Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Jul 2001 10:18:48 -0700 (PDT)
From:      Matt Dillon <dillon@earth.backplane.com>
To:        Luigi Rizzo <luigi@info.iet.unipi.it>
Cc:        Tim <tim@futuresouth.com>, Leo Bicknell <bicknell@ufp.org>, Drew Eckhardt <drew@PoohSticks.ORG>, hackers@FreeBSD.ORG
Subject:   Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.)
Message-ID:  <200107161718.f6GHImO15977@earth.backplane.com>
References:   <200107161420.QAA48911@info.iet.unipi.it>

next in thread | previous in thread | raw e-mail | index | archive | help
:i haven't seen the beginning of the thread but surely both altq
:and dummynet can help, with the CBQ/WFQ support.
:
:In the case of dummynet, you can pace incoming traffic as well,
:at your endpoint. This means you act after the bottleneck,
:but the effect is that this way
:you will delay acks, and so slow down the connection eating a lot of
:bandwidth, and in the steady state this keeps the queue very
:short even before the bottleneck.
:Much like what products like packeteer do.
:
:	cheers
:	luigi

    I don't know much about CBQ (Class Based Queuing) and WFQ (Weighted
    Fair Queueing), but my impression is that these protocols would only
    effect the transmit side (like the patch I posted) and would also have
    to be implemented at the router nodes rather then simply at the 
    end points.  Of course, for a modem your end point *is* a router node
    so that would probably work ok.

    The patch I posted, implementing bandwidth delay product adjustments
    to the transmit window, should work extremely well with a modem or
    DSL line (where the bandwidth restriction occurs near the end points
    rather then in the middle of the network), but again it only effects
    outgoing data.  I'm looking at Julian's algorithms to see if there
    is a receive side solution I can implement that wouldn't conflict 
    with the transmit side solution.

					-Matt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107161718.f6GHImO15977>