From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (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 37DC821F316 for ; Thu, 19 Nov 2015 01:22:46 -0800 (PST) Received: by obbww6 with SMTP id ww6so55515505obb.0 for ; Thu, 19 Nov 2015 01:22:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ILq/ZYM3jUbonsPs8jn0t/FGLltTrx+IB2+orkoxftg=; b=rI5NIhetzKO6SKE9jdWi8Rfru3dyNzudtQ65UDVPUc7ywSpAyS7qXUzrVrtrhE4VEi 6mytCKRBwIgM7X9h+OlROXHmR79kjCC02Qvdcrmx0Qzkem+01mkmuYoaAbl2LYE3dIJJ qZbgO+OEnzFW/8jWqgr28GYcv+qOWpC9RE/3YXakDeQkr1b0ClSGFKlsKFmRtzHPbIrP 3ZED8i5+ZM+H0tSnOrXGzYBAehppoXS7XMyWyJHF4Pc5vOsGJXtSCSNh4l3BRvzM+j00 dM8I/2SpixKwtCdf2FUms9//O31UY7i2BW6jz+eVQ6waX1ykZ+9BKU2y+shGXf+sPOUq Cm9g== MIME-Version: 1.0 X-Received: by 10.60.164.73 with SMTP id yo9mr4027666oeb.33.1447924965948; Thu, 19 Nov 2015 01:22:45 -0800 (PST) Received: by 10.202.50.130 with HTTP; Thu, 19 Nov 2015 01:22:45 -0800 (PST) Date: Thu, 19 Nov 2015 10:22:45 +0100 Message-ID: From: Dave Taht To: cake@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Cake] strict(er) priority model X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 09:23:09 -0000 There are a few circumstances where the inherent bandwidth/latency tradeoffs in cake are trumped by perceived needs for strict priority queues. One fairly common one is on boxes doing bgp, where the bgp flow "must" complete as fast as possible. There are probably other cases in the network routing world (how does ISIS exchange routes? ospf?) A common case for voip-ers is to strictly prioritize udp sip/rtp flows over everything else. Having a model available closer in implementation (and NOT the default) to the strict priority queues sch_fq and pfifo_fast have may ease adoption. ? then there are vlans and so on... Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! https://www.gofundme.com/savewifi