Tom Matthews writes: > (I understand the both the increased impact this has on the required memory > for the buffers and that it only relates to RFC1323-compliant systems. I'm > asking because I'm seeing NoCanPuts on a 1Gbps interface which has already > had the TCP and UDP recv_hiwat set to 64KB)
The "no canput" problem occurs much lower in the stack. Tuning TCP windows or UDP buffers won't fix a problem like that, so I think you're looking at the wrong issue here. That problem occurs when the STREAMS (networking) driver is flow-controlled by the upstream module -- 'ip' in this case. The driver calls canput(9E) and gets back zero as a response. It has nothing to do with the transport layer activity. I think you should be looking into either patches for your drivers (it's possible that you've got a bug here) or tuning guides for those Ethernet drivers. Are you, by chance, running Solaris 10 or older? Many of those "canput" problems are in older releases, and not in OpenSolaris due to changing internal design. If you are on an older release, you should be contacting Sun's support group instead. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
