From: erik quanstrom <quanstro@quanstro.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] rtl8169 gbe slow
Date: Thu, 18 Feb 2016 17:56:21 -0800 [thread overview]
Message-ID: <79b356fa-8def-4917-9007-fa111251a4bf@email.android.com> (raw)
In-Reply-To: <91DCC65B-33DB-493C-BF73-6AD2C520CF3B@ar.aichi-u.ac.jp>
the standard labs driver checks the speed during auto negotiation.
so it is often wrong.
- erik
On Feb 18, 2016 3:41 PM, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
>
> hello,
>
> rtl8169 is popular in cheap MB, so it is installed in my many MBs.
> however, cat /dev/kmesg claims:
> rtl8169: oui 0x732 phyno 1, macv = 0x3c000000 phyv = 0x0002
> #l0: rtl8169: 100Mbps port 0xD000 irq 10: 001fd0169891
>
> the “100Mbps" in the message is correct or not?
>
> I also feel rtl8169 is slow, so I replace on-board rtl8169 by intel’s card if possible.
>
>
>
> > 2016/02/18 22:22、erik quanstrom <quanstro@quanstro.net> のメール:
> >
> > the 8169 driver is pretty fast. I've measured it at more than 500mbps.
> > it sounds like something else is misbehaving. what does
> > /dev/irqstat say. I bet something is stuck.
> >
> > - erik
> >
> >
> > On Feb 18, 2016 3:30 AM, tlaronde@polynum.com wrote:
> >>
> >> Hello,
> >>
> >> I have finally managed to install plan9 on my new workstation.
> >>
> >> By putting back the keyboard on the PS2 connector, I have solved some
> >> unfelicities (with the USB->legacy emulation, the keyboard switched
> >> every other typing to UPPERCASE...).
> >>
> >> The mouse, still USB connected and hence "emulated" by the BIOS,
> >> does not react very gracefully but I will see if I can play with
> >> the acceleration and the resolution to have a better terminal. (Or
> >> if I manage to find a long enough cable to have a COM slot back since
> >> there is the bare connector on the motherboard; in this case I will go
> >> back to a com mouse and will be able to probe USB for other
> >> devices---external disks.)
> >>
> >> One thing is inconvenient: I have a rtl8169 gbe pci-e ether card, but
> >> when testing the compilation of kerTeX (it has been fixed: it works for
> >> the last release; rio to come for METAFONT), the throughput with hget is
> >> abysmal: 30kB/s... The disk is not a fault, reacting well enough (I have
> >> plenty of RAM and the blocks cache for fossil is set to 3000---it could
> >> be obviously higher).
> >>
> >> Setting the mtu to jumbo packet does not help.
> >>
> >> Is there something to tune or is it simply that the chip is not well
> >> supported?
> >>
> >> TIA
> >> --
> >> 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
> >>
> >>
>
>
>
next prev parent reply other threads:[~2016-02-19 1:56 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 [this message]
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
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=79b356fa-8def-4917-9007-fa111251a4bf@email.android.com \
--to=quanstro@quanstro.net \
--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).