Re: [PATCH net-next] remove TWKilled counter

Mon, Jan 21, 2019 at 3:14 PM peng yu wrote: > > > > Hello, I think the snmp.h didn't try to keep user-space compatibility, > > so we could delete LINUX_MIB_TIMEWAITKILLED counter. Do I > > misunderstand anything? > > I don't know. Maybe user-space doesn&#

Re: [PATCH net-next] remove TWKilled counter

Hello, I think the snmp.h didn't try to keep user-space compatibility, so we could delete LINUX_MIB_TIMEWAITKILLED counter. Do I misunderstand anything? On Thu, Jan 17, 2019 at 12:26 PM peng yu wrote: > > On Thu, Jan 17, 2019 at 10:07 AM Cong Wang wrote: > > > > On Thu,

Re: [PATCH net-next] remove TWKilled counter

On Thu, Jan 17, 2019 at 10:07 AM Cong Wang wrote: > > On Thu, Jan 17, 2019 at 3:43 AM yupeng wrote: > > diff --git a/include/uapi/linux/snmp.h b/include/uapi/linux/snmp.h > > index 86dc24a96c90..fb0a17337bf2 100644 > > --- a/include/uapi/linux/snmp.h > > +++ b/include/uapi/linux/snmp.h > > @@ -17

Re: [Patch net-next] call sk_dst_reset when set SO_DONTROUTE

ould stuck immediately after set SO_DONTROUTE to 1. On Wed, Dec 5, 2018 at 4:20 PM Eric Dumazet wrote: > > > > On 12/05/2018 04:13 PM, peng yu wrote: > > The SO_DONTROUTE doesn't impact the TCP receiving path, but it should > > block the ACK of the receiving packet. Wh

Re: [Patch net-next] call sk_dst_reset when set SO_DONTROUTE

The SO_DONTROUTE doesn't impact the TCP receiving path, but it should block the ACK of the receiving packet. When there are too many packets which are not ACKed, the client will stop to send packets, so the sock.recv on the server side won't receive data after it received some data. I extracted the

Re: [PATCH net-next] add part of TCP counts explanations in snmp_counters.rst

On Mon, Nov 19, 2018 at 10:51 AM Stephen Hemminger wrote: > > On Fri, 16 Nov 2018 11:17:40 -0800 > yupeng wrote: > > > +* TcpInSegs > > +Defined in `RFC1213 tcpInSegs`_ > > + > > +.. _RFC1213 tcpInSegs: https://tools.ietf.org/html/rfc1213#page-48 > > + > > +The number of packets received by the T

Re: [PATCH net-next v2] documentation of some IP/ICMP snmp counters

my changes depend on previous feedback: 1 group counters by protocol 2 remove all text which is pasted from RFC 3 about the simple command as 'ping', I hope to provide a full test steps, so I still keep them in the document 4 use capital letter for the abbreviated keywords 5 tried to fix grammar mi

a propose of snmp counter document

I'm planing to write a document which explains the meaning of the kernel snmp counters, and combine the explanations with some tests, because I found lots of the 'TcpExt' and 'IpExt' counters are not explained in any document. Here is a draft: https://github.com/yupeng0921/iproute2_learning/blob/ma

Re: [ftrace-bpf 1/5] add BPF_PROG_TYPE_FTRACE to bpf

> 1. anything bpf related has to go via net-next tree. I found there is a net-next git repo: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git I will use this repo for the further bpf-ftrace patch set. > 2. > this obviously breaks ABI. New types can only be added to the end. Sure,

Re: [iproute PATCH] ss: add detail explains of -m, -o, -e and -i options in ss man page

et me know. commit 9803d27de31028733de789495d78ff7a39385009 Author: yupeng Date: Wed Oct 25 21:12:21 2017 + add additional explain in ss man page Add detail explains of -m, -o, -e and -i options, which are not documented anywhere Signed-off-by: Peng Yu diff --git a/man/man8/ss.8 b/man/man8/ss.8 index 3be

[iproute PATCH] ss: add detail explains of -m, -o, -e and -i options in ss man page

commit 340a45f79395144bd14fdf9be1904c0036456b6e Author: yupeng Date: Tue Oct 24 23:55:29 2017 + add additional explain in ss man page Add detail explains of -m, -o, -e and -i options, which are not documented anywhere Signed-off-by: Peng Yu diff --git a/man/man8/ss.8 b/man