From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <595e28c2c25b6d648085e5d51c5d51f3@lilly.quanstro.net> References: <87C61423-7C13-4516-88B5-C2ABA7D32AA9@me.com> <595e28c2c25b6d648085e5d51c5d51f3@lilly.quanstro.net> Date: Thu, 7 May 2015 08:15:15 +0200 Message-ID: From: David du Colombier <0intro@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] fossil+venti performance question Topicbox-Message-UUID: 50159104-ead9-11e9-9d60-3106f5b1d025 > NOW is defined as MACHP(0)->ticks, so this is a pretty course timer > that can't go backwards on intel processors. this limits the timer's resolution to HZ, > which on 9atom is 1000, and 100 on pretty much anything else. further limiting the > resolution is the tcp retransmit timers which according to presotto are > /* bounded twixt 0.3 and 64 seconds */ > so i really doubt the retransmit timers are resending anything. if someone > has a system that isn't working right, please post /net/tcp//^(local remote status) > i'd like to have a look. The Venti listenner: cpu% cat /net/tcp/2/local ::!17034 cpu% cat /net/tcp/2/remote ::!0 cpu% cat /net/tcp/2/status Listen qin 0 qout 0 rq 0.0 srtt 4000 mdev 0 sst 65535 cwin 1460 swin 0>>0 rwin 65535>>0 qscale 0 timer.start 10 timer.count 0 rerecv 0 katimer.start 2400 katimer.count 0 The TCP connection from Fossil to Venti on the loopback: cpu% cat /net/tcp/3/local 127.0.0.1!57796 cpu% cat /net/tcp/3/remote 127.0.0.1!17034 cpu% cat /net/tcp/3/status Established qin 0 qout 0 rq 0.0 srtt 80 mdev 40 sst 1048560 cwin 258192 swin 1048560>>4 rwin 1048560>>4 qscale 4 timer.start 10 timer.count 10 rerecv 0 katimer.start 2400 katimer.count 427 -- David du Colombier