tcp failing to recover from a packet loss under 8.2-RELEASE?

Steven Hartland killing at multiplay.co.uk
Tue Aug 2 12:56:50 UTC 2011


----- Original Message ----- 
From: "Steven Hartland"
> I look forward to hearing peoples thoughts on what the actual fix
> should be: increased default nmbclusters, decreased nmbclusters =>
> maxsegments divisor, or something else?

Another useful piece of information is that even though maxsegments
is set as a read only tuneable, it can be changed on the fly by
changing kern.ipc.nmbclusters, which seems a bit strange tbh, so
possibly an oversight there somewhere.

Example:-

sysctl net.inet.tcp.reass.maxsegments=16464
sysctl: oid 'net.inet.tcp.reass.maxsegments' is a read only tunable
sysctl: Tunable values are set in /boot/loader.conf

sysctl net.inet.tcp.reass.maxsegments
net.inet.tcp.reass.maxsegments: 1680

sysctl kern.ipc.nmbclusters=262144
kern.ipc.nmbclusters: 25600 -> 262144

sysctl net.inet.tcp.reass.maxsegments
net.inet.tcp.reass.maxsegments: 16464

    Regards
    Steve

================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster at multiplay.co.uk.



More information about the freebsd-net mailing list