We are seeing following assertions when running specweb99 with tcp_tso_win_divisor lowered to 4, 2 or 1 on linux 2.6.9 based kernels. KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stre
The issue is if you change the value while there are still existing sockets which used a previous value at least once. Looks like we'll have to cache this inside of the per-socket structure to fix th
Could you elaborate the code path that you've spotted that causes this when the divisor is changed? Perhaps we're not caching the MSS value everywhere where we should be? Cheers, -- Visit Openswan at
2.6.9 is known to have bugs in TCP book-keeping. Please try 2.6.10-rc2 instead. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home P
Unfortunately as we cannot upgrade to 2.6.10-rc2, i tried to locate all the TSO accounting related bugfixes that went in after 2.6.9 and came up with the following 4 patches. [TCP]: Fix new packet le
This doesn't work. You cannot expect upstream maintainers to work with you if you're not willing to or able to try things out with the latest kernels. I have an inkling as to the reason why you're re
Yes. You are right. It is a vendor kernel based on 2.6.9 along with some vendor specific kernel patches. I agree that it is not always possible to support older kernels and i was not expecting you to