Matthew Dillon wrote:
> :Cap the window size via the driver.  This will probably require
> :another attribute on all drivers, indicating "max allowable window
> :size" ("0" could mean "any", and be used as the default so that we
> :don't end up flaking out someone talking to Mars).
> 
>     It won't help.  The problem is that the server is sending more
>     data then the client USB adapter can handle.  If the client limits
>     its window size with the expectation that the server will send it
>     small packets, then any *other* transfer that uses larger packets
>     will have terrible performance.

I'm talking about capping the maximum negotiable window size
over the USB adapter...

How can this cause problems, since (1) the only thing we are talking
about is window size, not packet size (MTU), and (2) the only thing
it will effect is the TCP stream post negotiation, so it should not
result in a slowdown for any virtual circuit other than those that
*NEED* a slowdown?

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to