From: Eric Dumazet <eric.dumazet@gmail.com>
To: liujian <liujian56@huawei.com>
Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru,
yoshfuji@linux-ipv6.org, edumazet@google.com, ycheng@google.com,
hkchu@google.com, netdev@vger.kernel.org, weiyongjun1@huawei.com,
wangkefeng 00227729 <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH] tcp: TCP_USER_TIMEOUT can not work in tcp_probe_timer()
Date: Tue, 12 Sep 2017 08:38:06 -0700 [thread overview]
Message-ID: <1505230686.15310.141.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <1505228700.15310.138.camel@edumazet-glaptop3.roam.corp.google.com>
On Tue, 2017-09-12 at 08:05 -0700, Eric Dumazet wrote:
> On Tue, 2017-09-12 at 14:08 +0800, liujian wrote:
> > Hi,
> >
> > In the scenario, tcp server side IP changed, and at that memont,
> > userspace application still send data continuously;
> > tcp_send_head(sk)'s timestamp always be refreshed.
> >
> > Here is the packetdrill script:
> >
> > 0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3
> > +0 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
> > +0 bind(3, ..., ...) = 0
> > +0 listen(3, 1) = 0
> >
> > +0 < S 0:0(0) win 0 <mss 1460,sackOK,nop,nop,nop,wscale 7>
> > +0 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK,nop,wscale 7>
> >
> > +.1 < . 1:1(0) ack 1 win 65530
> > +0 accept(3, ..., ...) = 4
> >
> > +0 setsockopt(4, SOL_TCP, TCP_USER_TIMEOUT, [3000], 4) = 0
> > +0 write(4, ..., 24) = 24
> > +0 > P. 1:25(24) ack 1 win 229
> > +.1 < . 1:1(0) ack 25 win 65530
> >
> > //change the ipaddress
> > +1 `ifconfig tun0 192.168.0.10/16`
> >
> > +1 write(4, ..., 24) = 24
> > +1 write(4, ..., 24) = 24
> > +1 write(4, ..., 24) = 24
> > +1 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> > +3 write(4, ..., 24) = 24
> >
> > +0 `ifconfig tun0 192.168.0.1/16`
> > +0 < . 1:1(0) ack 1 win 1000
> > +0 write(4, ..., 24) = -1
> >
> >
>
> This has nothing to do with the code patch you have changed.
>
> How have you tested your patch exactly ?
>
lpaa23:~# ss -toenmi src :8080
State Recv-Q Send-Q Local Address:Port Peer
Address:Port
ESTAB 0 144 192.168.134.161:8080
192.0.2.1:51165 timer:(persist,8.262ms,5) ino:1
82083 sk:3 <->
skmem:(r0,rb359040,t0,tb46080,f1792,w2304,o0,bl0,d0) sack cubic
wscale:7,8 rto:301 backoff:5 rtt:100.127/37.576
mss:1460 rcvmss:536 advmss:1460 cwnd:10 bytes_acked:24 segs_out:12
segs_in:3 data_segs_out:12 send 1.2Mbps lastsnd:1370 l
astrcv:13348 lastack:13248 pacing_rate 2.3Mbps delivery_rate 116.7Kbps
app_limited busy:11346ms rcv_space:29200 notsent:1
44 minrtt:100.043
This is the typical RTO timer, not zero window probe.
next prev parent reply other threads:[~2017-09-12 15:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 6:27 [PATCH] tcp: TCP_USER_TIMEOUT can not work in tcp_probe_timer() liujian56
2017-09-11 14:49 ` Eric Dumazet
2017-09-11 15:13 ` Eric Dumazet
2017-09-11 15:22 ` Eric Dumazet
2017-09-12 6:08 ` liujian
2017-09-12 15:05 ` Eric Dumazet
2017-09-12 15:38 ` Eric Dumazet [this message]
2017-09-13 6:56 ` liujian
2017-09-13 7:15 ` liujian
2017-09-13 14:40 ` Eric Dumazet
2017-09-14 3:30 ` [PATCH net] tcp: update skb->skb_mstamp more carefully Eric Dumazet
2017-09-14 8:17 ` liujian
2017-09-14 13:57 ` Neal Cardwell
2017-09-14 16:32 ` Yuchung Cheng
2017-09-14 16:41 ` Soheil Hassas Yeganeh
2017-09-15 21:37 ` David Miller
2017-09-15 23:16 ` Eric Dumazet
2017-09-15 23:47 ` [PATCH net] tcp: fix data delivery rate Eric Dumazet
2017-09-16 1:33 ` Soheil Hassas Yeganeh
2017-09-16 16:07 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1505230686.15310.141.camel@edumazet-glaptop3.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkchu@google.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=liujian56@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=ycheng@google.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox