On Fri, Sep 13, 2019 at 10:29 AM Thomas Higdon wrote:
>
> On Thu, Sep 12, 2019 at 10:14:33AM +0100, Dave Taht wrote:
> > On Thu, Sep 12, 2019 at 1:59 AM Neal Cardwell wrote:
> > >
> > > On Wed, Sep 11, 2019 at 6:32 PM Thomas Higdon wrote:
> > > >
> > > > Neal Cardwell mentioned that rcv_wnd woul
On Thu, Sep 12, 2019 at 10:14:33AM +0100, Dave Taht wrote:
> On Thu, Sep 12, 2019 at 1:59 AM Neal Cardwell wrote:
> >
> > On Wed, Sep 11, 2019 at 6:32 PM Thomas Higdon wrote:
> > >
> > > Neal Cardwell mentioned that rcv_wnd would be useful for helping
> > > diagnose whether a flow is receive-wind
On Thu, Sep 12, 2019 at 1:59 AM Neal Cardwell wrote:
>
> On Wed, Sep 11, 2019 at 6:32 PM Thomas Higdon wrote:
> >
> > Neal Cardwell mentioned that rcv_wnd would be useful for helping
> > diagnose whether a flow is receive-window-limited at a given instant.
> >
> > This serves the purpose of addin
On Wed, Sep 11, 2019 at 6:32 PM Thomas Higdon wrote:
>
> Neal Cardwell mentioned that rcv_wnd would be useful for helping
> diagnose whether a flow is receive-window-limited at a given instant.
>
> This serves the purpose of adding an additional __u32 to avoid the
> would-be hole caused by the add
Neal Cardwell mentioned that rcv_wnd would be useful for helping
diagnose whether a flow is receive-window-limited at a given instant.
This serves the purpose of adding an additional __u32 to avoid the
would-be hole caused by the addition of the tcpi_rcvi_ooopack field.
Signed-off-by: Thomas Higd
