From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 5460121F520; Fri, 29 Aug 2014 10:15:11 -0700 (PDT) Received: by mail-la0-f52.google.com with SMTP id ty20so3125775lab.11 for ; Fri, 29 Aug 2014 10:15:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Cswd9OVMpganI3DMKeHJJ33s+JT0iSI7C4gg7lvl6+Y=; b=gVWWXOlrSC0EdI4xr4OgPQyJ4Kwv3Yue5pdIOqmL34fdAYD5WO4a2t2eG3KLoP73Mm U9+ZG2nqIVWmDsaS0vqBNbN4KpbQdKkt4SNjGx/+IKQxSZlp85B/5Sto3O2tjpPl+go2 aAFpvkWQfF+u9dmO6FOof98thBbet3J/fzp4J3o2+444yenuG4vTj1YGS3DNGW1wHT2J zA2Rs1yd3e/KTeOXiMagcyqXAeafFgHpCbYh7tzujPk7kICoCkV3vMwjXk2EcUnCPRUM ZEKwsn/IzdnJfJcfH4+h3BIYMF1ywij0Xg9n59EH8x84IZWQmEx5P4eola2np94dHpkz UmHA== X-Received: by 10.153.6.39 with SMTP id cr7mr12478813lad.66.1409332508624; Fri, 29 Aug 2014 10:15:08 -0700 (PDT) Received: from bass.home.chromatix.fi (188-67-224-93.bb.dnainternet.fi. [188.67.224.93]) by mx.google.com with ESMTPSA id bc5sm330713lab.30.2014.08.29.10.15.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 29 Aug 2014 10:15:07 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Jonathan Morton In-Reply-To: Date: Fri, 29 Aug 2014 20:15:05 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Aaron Wood X-Mailer: Apple Mail (2.1085) Cc: cerowrt-devel , bloat Subject: Re: [Bloat] Comcast upped service levels -> WNDR3800 can't cope... X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2014 17:15:12 -0000 On 29 Aug, 2014, at 7:57 pm, Aaron Wood wrote: > That's roughly 10K cpu cycles per packet, which seems like an awful = lot. I could analyse the chief algorithms to see how many clock cycles per = packet are theoretically possible - a number one could approach with an = embedded core in the NIC, rather than as part of a full kernel. - Jonathan Morton