On 05/17/18 at 03:45P, David Miller wrote:
> From: Yuchung Cheng
> Date: Wed, 16 May 2018 16:40:09 -0700
>
> > This patch set implements the features correspond to the
> > draft-ietf-tcpm-rack-03 version of the RACK draft.
> > https://datatracker.ietf.org/meeting/101/materials/slides-101-tcpm-upd
On 02/13/18 at 05:11P, Yuchung Cheng wrote:
> On Tue, Feb 13, 2018 at 4:27 PM, hiren panchasara
> wrote:
> >
> > Looking at current net-next to understand an aspect of TLP (tail loss
> > probe) implementation.
> >
> > https://tools.ietf.org/html/draft-ietf-tcp
Looking at current net-next to understand an aspect of TLP (tail loss
probe) implementation.
https://tools.ietf.org/html/draft-ietf-tcpm-rack-02 is the source of
truth now for TLP and 6.2.1. Phase 1: Scheduling a loss probe
Step 1: Check conditions for scheduling a PTO. has following as one of
th
On 09/18/17 at 02:46P, Yuchung Cheng wrote:
> On Mon, Sep 18, 2017 at 2:29 PM, hiren panchasara
> wrote:
> > On 09/18/17 at 02:18P, Eric Dumazet wrote:
> >> On Mon, 2017-09-18 at 13:14 -0700, hiren panchasara wrote:
> >> > Hi all, I am trying to disable rack
On 09/18/17 at 02:29P, hiren panchasara wrote:
> On 09/18/17 at 02:18P, Eric Dumazet wrote:
> > On Mon, 2017-09-18 at 13:14 -0700, hiren panchasara wrote:
> > > Hi all, I am trying to disable rack to see 3dupacks in action during
> > > loss-detection but based on the
On 09/18/17 at 02:18P, Eric Dumazet wrote:
> On Mon, 2017-09-18 at 13:14 -0700, hiren panchasara wrote:
> > Hi all, I am trying to disable rack to see 3dupacks in action during
> > loss-detection but based on the pcap, I see that it's still trigger
> > loss-recovery on
Hi all, I am trying to disable rack to see 3dupacks in action during
loss-detection but based on the pcap, I see that it's still trigger
loss-recovery on the first SACK (as if RACK is still enabled/active).
Here is what I did to disable rack:
net.ipv4.tcp_recovery = 0
I've also disabled metrics:
On 04/06/17 at 05:45P, Stephen Hemminger wrote:
> On Wed, 5 Apr 2017 12:40:09 -0700
> hiren panchasara wrote:
>
> > (New to linux and first-time poster so please guide me if needed.)
> >
> > Upon using tcpprobe I realized that it prints snd_nxt and snd_una as hex
&
(New to linux and first-time poster so please guide me if needed.)
Upon using tcpprobe I realized that it prints snd_nxt and snd_una as hex
which makes it harder to read and compare with tcpdump for example.
Not sure if that is intentional. If not, a simple patch like this would
print them as d
