From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 22 Feb 2016 16:34:41 +0100
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20160222153441.GB2923@polynum.com>
References: <20160222150546.GA2988@polynum.com>
	<7d38e04221ef6aa3c0db54c931414930@proxima.alt.za>
MIME-Version: 1.0
In-Reply-To: <7d38e04221ef6aa3c0db54c931414930@proxima.alt.za>
User-Agent: Mutt/1.5.24 (2015-08-30)
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: Re: [9fans] rtl8169 gbe slow
Topicbox-Message-UUID: 87bbf7ec-ead9-11e9-9d60-3106f5b1d025

On Mon, Feb 22, 2016 at 05:19:04PM +0200, lucio@proxima.alt.za wrote:
> > I have hence to ask the provider if there is something,
> > in their configuration, that could explain this
>
> If you can run NetBSD at the same time as Plan 9, you could also use
> tcpdump (whatever its current impersonation) to monitor the link.
> It's been a long time since I last did that, but it may be revealing.
>

I will have to snoopy and tcpdump as a last resort to try to have a clue.
Just looking at the numbers, it's like Plan9 only assembling packets in
order (1500 bytes every latency time), and reasking for packet n+1 after
receiving packet n, whatever packets being received in the mean time.
But I'm out of my depth: I'm not a TCP/IP expert.
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                     http://www.arts-po.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C