On 9/3/15 7:13 PM, Lawrence Stewart wrote:
On 09/03/15 10:54, hiren panchasara wrote:
I am failing to understand the reason behind this behavior.
What should the congestion window (snd_cwnd) be set to when we hit loss?
It seems that we set it to 1 segment right now.
On 09/03/15 at 09:13P, Lawrence Stewart wrote:
> On 09/03/15 10:54, hiren panchasara wrote:
> > I am failing to understand the reason behind this behavior.
> >
> > What should the congestion window (snd_cwnd) be set to when we hit loss?
> > It seems that we set it to 1 segment right now.
> >
On 09/03/15 at 09:16P, hiren panchasara wrote:
> On 09/03/15 at 09:13P, Lawrence Stewart wrote:
[skip]
> >
> > You want to read up about window inflation during fast recovery in RFC
> > 5681 followed by 3782, and then consult Stevens vol 2 to understand how
> > variables are used for different
On 09/03/15 10:54, hiren panchasara wrote:
> I am failing to understand the reason behind this behavior.
>
> What should the congestion window (snd_cwnd) be set to when we hit loss?
> It seems that we set it to 1 segment right now.
>
On 09/03/15 at 10:53P, hiren panchasara wrote:
> On 09/03/15 at 09:16P, hiren panchasara wrote:
> > On 09/03/15 at 09:13P, Lawrence Stewart wrote:
> [skip]
> > >
> > > You want to read up about window inflation during fast recovery in RFC
> > > 5681 followed by 3782, and then consult Stevens vol
I am failing to understand the reason behind this behavior.
What should the congestion window (snd_cwnd) be set to when we hit loss?
It seems that we set it to 1 segment right now.
https://svnweb.freebsd.org/base/head/sys/netinet/tcp_input.c?revision=286227=markup#l2531
I also see that in the
