Re: [RFC PATCH net-next v2] tcp: Add RFC4898 tcpEStatsPerfDataSegsOut/In

2016-03-08 Thread David Miller
From: Marcelo Ricardo Leitner Date: Tue, 8 Mar 2016 16:41:54 -0300 > On Mon, Mar 07, 2016 at 06:01:05PM -0800, Martin KaFai Lau wrote: >> v2: >> Rework based on recent fix by Eric: >> commit a9d99ce28ed3 ("tcp: fix tcpi_segs_in after connection establishment") >> >> v1: > > Patch itself looks g

Re: [RFC PATCH net-next v2] tcp: Add RFC4898 tcpEStatsPerfDataSegsOut/In

2016-03-08 Thread Marcelo Ricardo Leitner
On Mon, Mar 07, 2016 at 06:01:05PM -0800, Martin KaFai Lau wrote: > v2: > Rework based on recent fix by Eric: > commit a9d99ce28ed3 ("tcp: fix tcpi_segs_in after connection establishment") > > v1: Patch itself looks good to me, just this patch history is better placed on the Notes region (togethe

[RFC PATCH net-next v2] tcp: Add RFC4898 tcpEStatsPerfDataSegsOut/In

2016-03-07 Thread Martin KaFai Lau
v2: Rework based on recent fix by Eric: commit a9d99ce28ed3 ("tcp: fix tcpi_segs_in after connection establishment") v1: Per RFC4898, they count segments sent/received containing a positive length data segment (that includes retransmission segments carrying data). Unlike tcpi_segs_out/in, tcpi_da