From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iy0-f171.google.com (mail-iy0-f171.google.com [209.85.210.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id BD77B20045C for ; Tue, 24 May 2011 07:33:33 -0700 (PDT) Received: by iyi20 with SMTP id 20so8184536iyi.16 for ; Tue, 24 May 2011 07:46:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=3MNW2HjqhGYd81v8rkJcj3Ac/+76SBNeL6xsyPGlK+8=; b=SeFgacg55niWLk8mDVcDRvTdHuPTK8y6M7WlYf1rsdY+I+YwVy59cfAuHsE67ly30D +EPKA9enIIcMTGlLdsliK6g4RdtpwrJac7TSERQWaVFetsl7iveMMotH+ur7TpOyTuaf 1uPBPlD5xLocHaGZFb8Nl0AqIn+LWHhk0rGMk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=RAcwF6IeP6L01LNL8991s6toTY1/0iXViZO7Tee7U750EvmdKza010qsLhFYFjWTIy v67kmoEPL5izD9a4ILgwz82IUtUECJPmVKtx/LJBKfpmDo1xFz6CIQt3bcbRr0u3Wel3 tLjUeCGfQODO+F28L39J5Me2JFfzaouF9VJCE= MIME-Version: 1.0 Received: by 10.42.177.3 with SMTP id bg3mr10011219icb.359.1306248419121; Tue, 24 May 2011 07:46:59 -0700 (PDT) Received: by 10.231.35.139 with HTTP; Tue, 24 May 2011 07:46:59 -0700 (PDT) Date: Tue, 24 May 2011 14:46:59 +0000 Message-ID: Subject: still coping with zero packet loss over wireless From: Dave Taht To: bloat-devel@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=90e6ba6e8e68029afa04a406a9b8 X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 14:33:34 -0000 --90e6ba6e8e68029afa04a406a9b8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable yesterday I finally got a chance to move a few dozen meters out of the lab and test the latest build of uberwrt "capetown" and debloat-testing. I'd hoped with the debloating techniques in place in capetown - reduced buffers (4), reduced sw retries (2), hw retries (2, or so I thought) I'd actually see some packet loss. and what I saw instead, was pings that would take as long as 1.6 seconds to complete, and zero packet loss until I moved completely out of range of the router. I never thought it would be so hard to lose a packet in my life! Is there some system tunable, somewhere, in the linux wireless stack that I've missed, in getting packets to actually fail in 10s of ms? --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://the-edge.blogspot.com --90e6ba6e8e68029afa04a406a9b8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable yesterday I finally got a chance to move a few dozen meters out of the lab = and test the latest build of uberwrt "capetown" and debloat-testi= ng.

I'd hoped with the debloating techniques in place in capetow= n - reduced buffers (4), reduced sw retries (2), hw retries (2, or so I tho= ught) I'd actually see some packet loss.

and what I saw instead, was pings that would take as long as 1.6 second= s to complete, and zero packet loss until I moved completely out of range o= f the router.

I never thought it would be so hard to lose a packet i= n my life!

Is there some system tunable, somewhere, in the linux wireless stack th= at I've missed, in getting packets to actually fail in 10s of ms?

--
Dave T=E4ht
SKYPE: davetaht
US Tel: 1-239-829= -5608
http://the-edge.= blogspot.com
--90e6ba6e8e68029afa04a406a9b8--