On Sun, 14 Oct 2007 10:02:45 +0900 Komuro <[EMAIL PROTECTED]> wrote: > Dear David > > Actually, tcp_sk(sk)->snd_ssthresh is not initialized, > if initial_ssthresh is 0. > > The patch should be > > static void bictcp_init(struct sock *sk) > { > bictcp_reset(inet_csk_ca(sk)); > - if (initial_ssthresh) > - tcp_sk(sk)->snd_ssthresh = initial_ssthresh; > + > + tcp_sk(sk)->snd_ssthresh = initial_ssthresh; > } >
In which case it is zero because that is the default value. If you want to make arguments about sshtresh value, you need to provide tcp traces of good vs problematic connection and get a good idea of what the intermediate path and remote host OS is. Since you are the first to raise the issue, you will have to provide a lot of evidence to overcome the developer suspicion that the problem is due to buggy middle boxes, hardware or the other end. -- Stephen Hemminger <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/