From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 7EE0B3B29E for ; Tue, 11 Dec 2018 13:32:55 -0500 (EST) Received: by mail-ot1-x32d.google.com with SMTP id f18so14995544otl.11 for ; Tue, 11 Dec 2018 10:32:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FAVQWnumah8Y9Qx4UJstPcEA+jdcZreYE2trWTyxjiw=; b=JeP1Mzu3PI/4L9rnP0JuetuTAIyd5gYmwyynXScFK6o4zOzPA2DRQao7keyWeTqJQK KY/ilBM2jxrNo/VeT0nMGNGSilQl5n9c2ab8NiRw/0TG6Na8+XzOhUodjGAN/zlKcN1W qaAGEVPbdJJ1mHhowxK63U2ZTEBwg3EkH/lcs+beC4XzKrU5Umy/bBlgmKqwO1HJ/Q3Y 0tjQEW4hljzAmToix2Sxr7XXEgwlxONUcCp4ZlZO++vWnfRI4Tsh0TP0pDluKpycLofy zVkM6IjOY4/GMdyO8veV9zAEZ9mtSg2LuNxtcI9H6n42RTCiwCkoY+eYxvP/pDl3DGgu 3Jvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FAVQWnumah8Y9Qx4UJstPcEA+jdcZreYE2trWTyxjiw=; b=N1o5CfKhE5u005iSDjZY357YQjXjQw1tmffTydjLiLKJsunCcS2YOtxskf5QXYhKWv f+pYl81H8iLUQv3Arl3DxjYIV7IEj+/xQ7Cp+Y/sxeZY4pYRf64c3qN8hfLtb+7ImtfE PZFsU6x8udGHtQ74vywgGluaON7oEby+cUXoUv8YyCGAecAmy0wRKmXWAO3ZnZup3vwM KL86L7FS8EGK2s0PkdR56LuUsrPnJAXzBP1JMwXKdHgnfVl6tZI1nKCOmrJ6BKxoLiL+ Q87p5jHsfqUVS33CT7EYm/TLil3kIP7MOKGhhjqWVKcOfnyPlMUDH19Sb57iErQWKb7k yopQ== X-Gm-Message-State: AA+aEWYievHGPmhd8XnJQpEBmOJvAs9Fnba978CpjahGryz4Y0buzIA9 ynDZXrPKnvGchEFxyvGvJGjvuanZnlNIHE3G7n4= X-Google-Smtp-Source: AFSGD/XVFwY+ctVbNlhVGL6UNA+VVlDqM1h6EdE1/irYgdTVOX9GnCkVZGo3Ra1qLwh1DdviPfm5jHvk/N49aJvMuUA= X-Received: by 2002:a9d:346:: with SMTP id 64mr12732158otv.90.1544553174723; Tue, 11 Dec 2018 10:32:54 -0800 (PST) MIME-Version: 1.0 References: <87bm5zgkkg.fsf@toke.dk> In-Reply-To: <87bm5zgkkg.fsf@toke.dk> From: Aaron Wood Date: Tue, 11 Dec 2018 10:32:43 -0800 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: Dave Taht , cerowrt-devel Content-Type: multipart/alternative; boundary="00000000000050f21b057cc34f80" Subject: Re: [Cerowrt-devel] fq_pie for linux X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Dec 2018 18:32:55 -0000 --00000000000050f21b057cc34f80 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Dec 5, 2018 at 11:51 PM Toke H=C3=B8iland-J=C3=B8rgensen wrote: > Dave Taht writes: > > > https://github.com/gautamramk/FQ-PIE-for-Linux-Kernel/issues/2 > > With all the variants of fq+AQM, maybe decoupling the FQ part and the > AQM part would be worthwhile, instead of reimplementing it for each > variant... > That's a great idea, Toke. There are a lot of places where I think it could work well, especially if it took a pluggable hash function for the hashing (at which point it's very general-purpose, and works on all sorts of different kinds of packets and workloads). That would let it be used for userspace VPN links (as an example), or within QUIC (or similar), where the kernel can't see the embedded flows that are hidden by the TLS encryption. And having it pluggable in the kernel would also allow IPSec to work without bloat (last I checked it was horribly bufferbloated, but that was ~5 years ago). --00000000000050f21b057cc34f80 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Dec 5, 2018 at 11:51 PM Toke H=C3=B8iland-J=C3=B8r= gensen <toke@toke.dk> wrote:
<= div class=3D"gmail_quote">
Dave Taht <dave.taht@gmail.com> writes:

> https://github.com/gautamramk/FQ-= PIE-for-Linux-Kernel/issues/2

With all the variants of fq+AQM, maybe decoupling the FQ part and the
AQM part would be worthwhile, instead of reimplementing it for each
variant...

That's a great idea, Tok= e.=C2=A0 There are a lot of places where I think it could work well, especi= ally if it took a pluggable hash function for the hashing (at which point i= t's very general-purpose, and works on all sorts of different kinds of = packets and workloads).=C2=A0 That would let it be used for userspace VPN l= inks (as an example), or within QUIC (or similar), where the kernel can'= ;t see the embedded flows that are hidden by the TLS encryption.
=
And having it pluggable in the kernel would also allow IPSec= to work without bloat (last I checked it was horribly bufferbloated, but t= hat was ~5 years ago).
--00000000000050f21b057cc34f80--