From: Kenny Lasse Hoff Levinsen <kennylevinsen@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] rtl8169 gbe slow
Date: Tue, 23 Feb 2016 18:54:25 +0100 [thread overview]
Message-ID: <8D18C6B4-B5AB-40DA-9DD7-097C9735A1EA@gmail.com> (raw)
In-Reply-To: <e065249358d59919a37d021f7c548534@lilly.quanstro.net>
Just in case you want a another point of reference to eliminate weirdness with the specific box: http://de.kl.wtf/f/10mburandom
Linode Arch Linux box in Frankfurt, serving you with a pretty standard usage of Go’s http server. Should count as a “stock linux box with a non-weird HTTP server”.
if you add an “s”, you get TLS. If you add a “0”, you get 100MB. If you remove a country code, it goes through Cloudflare. You’ll have to guess where to insert and remove those characters yourself, though!
Best regards,
Kenny Levinsen
> On 23 Feb 2016, at 18:38, erik quanstrom <quanstro@quanstro.net> 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
>
next prev parent reply other threads:[~2016-02-23 17:54 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 11:30 tlaronde
2016-02-18 13:22 ` erik quanstrom
2016-02-18 23:41 ` arisawa
2016-02-19 1:56 ` erik quanstrom
2016-02-19 15:17 ` erik quanstrom
2016-02-19 12:52 ` tlaronde
2016-02-19 15:13 ` erik quanstrom
2016-02-19 17:11 ` tlaronde
2016-02-20 10:32 ` tlaronde
2016-02-20 11:23 ` Kenny Lasse Hoff Levinsen
2016-02-20 12:11 ` tlaronde
2016-02-20 13:31 ` hiro
2016-02-20 14:01 ` tlaronde
2016-02-20 14:06 ` lucio
2016-02-20 14:22 ` tlaronde
2016-02-20 17:20 ` erik quanstrom
2016-02-20 17:45 ` tlaronde
2016-02-20 19:26 ` erik quanstrom
2016-02-20 19:41 ` Mark van Atten
2016-02-20 20:18 ` tlaronde
2016-02-20 20:18 ` tlaronde
2016-02-22 9:14 ` tlaronde
2016-02-22 9:40 ` Mark van Atten
2016-02-22 10:10 ` tlaronde
2016-02-22 10:15 ` lucio
2016-02-22 11:05 ` tlaronde
2016-02-22 11:06 ` Richard Miller
2016-02-22 11:40 ` tlaronde
2016-02-22 12:00 ` lucio
2016-02-22 12:16 ` tlaronde
2016-02-22 12:17 ` Richard Miller
2016-02-22 12:29 ` Mark van Atten
2016-02-22 12:47 ` tlaronde
2016-02-22 12:52 ` Mark van Atten
2016-02-22 13:02 ` tlaronde
2016-02-22 13:20 ` erik quanstrom
2016-02-22 15:05 ` tlaronde
2016-02-22 15:19 ` lucio
2016-02-22 15:34 ` tlaronde
2016-02-22 15:43 ` lucio
2016-02-22 13:13 ` tlaronde
2016-02-22 13:29 ` lucio
2016-02-22 13:39 ` David du Colombier
2016-02-22 14:39 ` rod
2016-02-22 15:12 ` tlaronde
2016-02-22 15:21 ` stanley lieber
2016-02-22 15:27 ` tlaronde
2016-02-22 15:45 ` erik quanstrom
2016-02-22 15:46 ` David du Colombier
2016-02-22 16:28 ` Kenny Lasse Hoff Levinsen
2016-02-22 16:40 ` lucio
2016-02-22 16:57 ` Kenny Lasse Hoff Levinsen
2016-02-22 17:03 ` [9fans] FP instructions in note handlers (Was: rtl8169 gbe slow) lucio
2016-02-23 10:36 ` hiro
2016-02-22 16:45 ` [9fans] rtl8169 gbe slow rod
2016-02-22 16:57 ` tlaronde
2016-02-22 17:13 ` David du Colombier
2016-02-22 17:57 ` Skip Tavakkolian
2016-02-23 10:34 ` hiro
2016-02-23 12:24 ` erik quanstrom
2016-02-23 12:30 ` hiro
2016-02-23 12:37 ` hiro
2016-02-23 12:40 ` hiro
2016-02-23 12:48 ` hiro
2016-02-23 15:16 ` erik quanstrom
2016-02-23 17:27 ` hiro
2016-02-23 15:17 ` erik quanstrom
2016-02-23 17:24 ` hiro
2016-02-23 17:38 ` erik quanstrom
2016-02-23 17:50 ` hiro
2016-02-23 18:16 ` erik quanstrom
2016-02-23 18:38 ` hiro
2016-02-23 19:19 ` erik quanstrom
2016-02-23 19:35 ` hiro
2016-02-23 20:21 ` tlaronde
2016-02-23 17:54 ` Kenny Lasse Hoff Levinsen [this message]
2016-02-23 18:08 ` erik quanstrom
2016-02-23 17:48 ` lucio
2016-02-23 17:52 ` hiro
2016-02-23 15:18 ` erik quanstrom
2016-02-22 15:44 ` erik quanstrom
2016-02-20 19:07 ` tlaronde
2016-02-20 19:21 ` erik quanstrom
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=8D18C6B4-B5AB-40DA-9DD7-097C9735A1EA@gmail.com \
--to=kennylevinsen@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).