So how do you speculate that they are managing a greater packet size?
Also, it doesn't explain why the input limit on 2.0.36 is 51792 bytes
coming from Solaris 2.5.1 and 51797 bytes coming from Linux 2.1.131.
It's no longer in the realm of a few dozen bytes of protocol overhead!
Further, if the limit is 65535 minus X bytes of header, shouldn't the
implementation return EMSGSIZE if the write(2) call exceeds 65535-X ?
Regards,
Richard....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/