From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rick.jones2@hp.com>
Received: from g6t1526.atlanta.hp.com (g6t1526.atlanta.hp.com [15.193.200.69])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "smtp.hp.com",
	Issuer "VeriSign Class 3 Secure Server CA - G3" (verified OK))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 7937D21F72D;
	Fri, 29 Aug 2014 10:03:18 -0700 (PDT)
Received: from g5t1633.atlanta.hp.com (g5t1633.atlanta.hp.com [16.201.144.132])
	by g6t1526.atlanta.hp.com (Postfix) with ESMTP id 4279612D;
	Fri, 29 Aug 2014 17:03:15 +0000 (UTC)
Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51])
	by g5t1633.atlanta.hp.com (Postfix) with ESMTP id BFD5587;
	Fri, 29 Aug 2014 17:03:14 +0000 (UTC)
Message-ID: <5400B252.9000401@hp.com>
Date: Fri, 29 Aug 2014 10:03:14 -0700
From: Rick Jones <rick.jones2@hp.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Aaron Wood <woody77@gmail.com>, bloat <bloat@lists.bufferbloat.net>, 
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
References: <CALQXh-Pkqh6Wq9xc9ky0ruztu74ziUoiaiG0LPr+DVLtDqz4mQ@mail.gmail.com>
In-Reply-To: <CALQXh-Pkqh6Wq9xc9ky0ruztu74ziUoiaiG0LPr+DVLtDqz4mQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Cerowrt-devel] [Bloat] Comcast upped service levels ->
	WNDR3800 can't cope...
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
	<cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Fri, 29 Aug 2014 17:03:18 -0000

On 08/29/2014 09:57 AM, Aaron Wood wrote:
> Or, we need to find a way to implement the system such that it doesn't
> max out a 680MHz mips core just to push 100Mbps of data.  That's roughly
> 10K cpu cycles per packet, which seems like an awful lot.  Unless the
> other problem is that the memory bus just can't keep up.  My experience
> of a lot of these processors is that the low-level offload engines have
> great DMA capabilities for "wire-speed" operation, but that the
> processor core itself can't move data to save it's life.

In the long ago and far away, it used to be opined that one 
could/would/should get 1 Mbit/s per MHz.  Though that may have been for 
a situation where there wasn't much besides just the plain TCP/IP stack 
running (eg without firewall bits etc going).

Does "perf" run on MIPS in the kernel you are running?

rick jones