From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan9 on Pi 3B+
Date: Thu, 5 Apr 2018 22:33:19 +0100 [thread overview]
Message-ID: <38a2cbeff1bce22286af152898b682a2@hamnavoe.com> (raw)
In-Reply-To: <BA4D9781-54BA-43C0-AA71-6DC047739727@quintile.net>
> do you any feeling why plan9 sees only 200Mbps ether?
>
> is it the stack design, how plan9 accesses the hardware? or maybe the 300Mbps quoted is only when using jumbo frames?
Jumbo frames might help if the bottleneck was in the ip stack,
but I think the limiting factor is the Plan 9 usb infrastructure,
which is written more for simplicity than for maximum speed.
prev parent reply other threads:[~2018-04-05 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1092190499.1253166.1522781548163.ref@mail.yahoo.com>
2018-04-03 18:52 ` Brian L. Stuart
2018-04-03 19:35 ` Erik Quanstrom
2018-04-03 21:05 ` Richard Miller
2018-04-04 0:30 ` Skip Tavakkolian
2018-04-05 14:17 ` Richard Miller
2018-04-05 15:03 ` Richard Miller
2018-04-05 17:02 ` Steve Simon
2018-04-05 20:25 ` Bakul Shah
2018-04-05 22:13 ` hiro
2018-04-05 22:40 ` Rui Carmo
2018-04-05 21:33 ` Richard Miller [this message]
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=38a2cbeff1bce22286af152898b682a2@hamnavoe.com \
--to=9fans@hamnavoe.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).