From: Chuck Anderson <cra@WPI.EDU>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] BQL, txqueue lengths and the internet of things
Date: Thu, 12 Jun 2014 23:49:56 -0400 [thread overview]
Message-ID: <20140613034955.GI4946@angus.ind.WPI.EDU> (raw)
In-Reply-To: <CAA93jw4-PKLwoOtoccUynO+BCAAJ8d4_UFJxYEmaZKOzAMH3OQ@mail.gmail.com>
On Thu, Jun 12, 2014 at 02:46:18PM -0700, Dave Taht wrote:
> > I'd bet the same could be done for
> > raspberry pi and perhaps my other toy the wandboard which has a gigE adapter
>
> Well, measure first? Many of the low end devices can't achieve gigE
> in the first place, rendering the BQL method somewhat moot.
>
> If you can provide a pointer to the right driver I can take a look.
> (dmesg | grep eth)
Mine's a Rasberry Pi model B running OpenELEC 4.0.4, an XBMC distro:
# uname -a
Linux OpenELEC 3.14.5 #1 PREEMPT Wed Jun 4 14:03:32 CEST 2014 armv6l GNU/Linux
# dmesg|grep eth
[ 2.652186] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:70:1c:6e
[ 18.188931] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 18.190252] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 19.720667] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[ 19.756150] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
So it looks to be 100meg, because it is plugged into a gig capable
switch but it comes up at 100. Confirmed with the hardware specs
here:
http://elinux.org/RPi_Hardware
prev parent reply other threads:[~2014-06-13 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 22:49 Dave Taht
2014-06-12 1:05 ` David P. Reed
2014-06-12 1:57 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2014-06-12 21:46 ` [Cerowrt-devel] " Dave Taht
2014-06-13 3:49 ` Chuck Anderson [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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140613034955.GI4946@angus.ind.WPI.EDU \
--to=cra@wpi.edu \
--cc=cerowrt-devel@lists.bufferbloat.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