Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] debloating the Pi, maybe not.
Date: Mon, 26 Nov 2012 16:10:43 +0100	[thread overview]
Message-ID: <6215800.d6FWbLqba3@linux-lqwf.site> (raw)
In-Reply-To: <CAA93jw5FYhjbMFGJUOdZ=iRAvyDjYeVVQaZSZARnb6V6kChMBA@mail.gmail.com>

On Friday 23 November 2012 17:43:24 Dave Taht wrote:
> I was donated a raspberry pi in cambridge and got it booted today.
> It's a very cool
> box, an arm6, running debian, with hard floating point, and getting a complete
> development environment running, getting it to do mesh networking,
> graphics, apache, etc, on a 16GB SD card, was a breeze.
> 
> But as for network performance:
> 
> It only comes up at 100Mbit, and as noted elsewhere the ethernet chip
> is hooked up over USB.
> 
> dmesg
> 
> [3.078644] smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at
> usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:18:fc:ac
> 
> The best the 3.2 kernel based networking can do is about 75Mbit/sec.
> This eats 68% of cpu in the "system" (sy in top) and 30% in si (system
> interrupt)

Wow. What did you do to saturate the system like this? Blow empty
UDP packages into the net?

> I had had some hope of this being a good box to put some test tools on,
> but with performance like this, I am back to leveraging the mips stuff.
> 
> That said, I do intend to poke at the driver and update to 3.6 when
> I get a chance, since we have patches lying around for both this
> chip and the usbnet code.

Nothing for performance in the mean time. Note that we don't try to
do interrupt mitigation in usbnet.

	Regards
		Oliver


  reply	other threads:[~2012-11-26 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 16:43 Dave Taht
2012-11-26 15:10 ` Oliver Neukum [this message]
2012-11-26 15:29   ` Dave Taht

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=6215800.d6FWbLqba3@linux-lqwf.site \
    --to=oneukum@suse.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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