Re: bandwidth for bkbits.net (good news)

Pascal Schmidt
2003-09-02T17:55:42Z

On Tue, 02 Sep 2003 09:00:20 +0200, you wrote in linux.kernel:

> Stop argueing. You can shape only outgoing packets, which means that the
> shaper must have a big uplink pipe and then shape that into a thin downlink
> pipe. In Larrys' case, the shaper must be on the ISP network before the T1.

For Larry's case, you're right. Nothing you can do to shape lots of
incoming TCP connections. However, if you're facing a few long-lived
TCP connections, you can shape them by dropping incoming packets (that
is, shaping the outgoing packets from the router/shaper to the LAN).
The sending side will adjust its rate after at most a few seconds.

That works perfectly for the case of reserving bandwidth for critical
services in the face of ongoing large downloads. That's something
a lot of people want and need, so it's not all that worseless per se.

--
Ciao,
Pascal
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, 02 Sep 2003 09:00:20 +0200, you wrote in linux.kernel:

> Stop argueing. You can shape only outgoing packets, which means that the
> shaper must have a big uplink pipe and then shape that into a thin downlink
> pipe. In Larrys' case, the shaper must be on the ISP network before the T1.

For Larry's case, you're right. Nothing you can do to shape lots of
incoming TCP connections. However, if you're facing a few long-lived
TCP connections, you can shape them by dropping incoming packets (that
is, shaping the outgoing packets from the router/shaper to the LAN).
The sending side will adjust its rate after at most a few seconds.

That works perfectly for the case of reserving bandwidth for critical
services in the face of ongoing large downloads. That's something
a lot of people want and need, so it's not all that worseless per se.

--
Ciao,
Pascal