From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <0fae2f7ad3be7bc68e270f67be6c3392@lilly.quanstro.net> Date: Tue, 23 Feb 2016 18:50:06 +0100 Message-ID: From: hiro <23hiro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] rtl8169 gbe slow Topicbox-Message-UUID: 894f8bdc-ead9-11e9-9d60-3106f5b1d025 which machine is in the west coast? the one your tracing on? is that hget or a web server on plan9? is this the same test as posted by david? where do you see out-of-window rxes? what does that even mean? On 2/23/16, erik quanstrom wrote: > On Tue Feb 23 09:25:53 PST 2016, 23hiro@gmail.com wrote: >> in the long run the rwin seems much higher (65535) than the number of >> bytes in flight (less than 3x1500 bytes). >> >> i just noticed that the minimum latency numbers seem way low. many >> latency samples appear at around 40ms and 100ms, but there's also >> outliers? below 1ms. i don't get how this pcap got produced. perhaps >> wireshark is also interpreting it wrong, or timestamps are broken... > >> > 26/status:Established qin 0 qout 0 rq 0.0 srtt 1256 mdev 628 sst 65535 >> > cwin >> > 4517 swin 5808>>0 rwin 65535>>4 qscale 0 timer.start 10 timer.count 10 >> > rerecv 0 katimer.start 2400 katimer.count 2400 >> >> where did you run this? > > machine on the us west coast. clearly we are prevoking some sort of odd > behavior > in this machine, but it's not clear to me what we're doing. > > the only clue we have is the out-of-window rxes. perhaps the sender is > scaling. > > - erik > >