From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vw0-f43.google.com (mail-vw0-f43.google.com [209.85.212.43]) (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 7F7EE20111A; Mon, 5 Dec 2011 18:03:06 -0800 (PST) Received: by vbbfq11 with SMTP id fq11so7841416vbb.16 for ; Mon, 05 Dec 2011 18:03:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fK6UlwMJAqHfD/tdKF+5Q5mkZGABXT/7/RmNiYd5acI=; b=EM3sliXuHfvOf/NGWGw9b1mI6JgseZPqCuJ+1N+TVDab7voBG14SZQXEyefj+7sK6K I0mngwypc/ca1fYdemNeJ4Ufk+SdDaAwGHr6C8qlEOUj5bEehOJmSCBLs5XOUe8XO8Ua DXm2fJEhIk4r7I69/ulSxxzqZr2uEv66htWKg= MIME-Version: 1.0 Received: by 10.52.66.35 with SMTP id c3mr7346464vdt.17.1323136985428; Mon, 05 Dec 2011 18:03:05 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.109.10 with HTTP; Mon, 5 Dec 2011 18:03:05 -0800 (PST) In-Reply-To: <1323082774.2670.40.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> References: <1323082774.2670.40.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> Date: Tue, 6 Dec 2011 10:03:05 +0800 X-Google-Sender-Auth: MoKvDhJtd9uxYAtIlyRygkXmQBw Message-ID: From: Adrian Chadd To: Eric Dumazet Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Thu, 08 Dec 2011 17:53:31 -0800 Cc: linux-wireless , netdev@vger.kernel.org, bloat-devel , bloat Subject: Re: [Bloat] Time in Queue, bufferbloat, and... our accidentally interplanetary network 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: Tue, 06 Dec 2011 02:03:06 -0000 Hi, For what it's worth, I've also been tinkering with time-in-queue for the wifi queue management in FreeBSD. I don't have anything public yet. What I have done actually seems to work quite well, when doing TX queue time-in-queue management. (I'm ignoring RX queue management for now.) Yes, I think a weighted random drop with both time-in-queue and queue depth would work well. I haven't sat down to model what it'd look like given some traffic profiles. I'll be sure to post some patches and results when I have them. :) Adrian