From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 198063B2A4 for ; Thu, 29 Nov 2018 03:34:36 -0500 (EST) Received: by mail-lf1-x12f.google.com with SMTP id i26so815024lfc.0 for ; Thu, 29 Nov 2018 00:34:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=69UPOyxx47Uw62yGDLLyCGxRX4/aVUZGqjtGeyv+o/k=; b=qfZJvNSrGouY5gMAk3IInoTpoOfA9H+VeaMUy2YdKbRlJR6ThQOd9brmYNv2bel/j8 xF8Iuy7zJpOdMIzQD1kDmV6Xvot/2NMwAu+O/XXjaB8qgEwGX5qrbU8O33Arb/eON4Eq mMp6JE46Ga6UDg+OM+gJyg5JqGBF5qPvvA1z+ZitJgCqz7M5fxkC/FLcsMxUdbv1yYGP DQy8UYgUXaFybY5FmQKJ1DyvM+EGNcZ9NhYJSzCxijcDtH7WS8LPSA5G/1dm1Wbj8sTK GhOX2oxggCQ63SlUpKGdtu7xgNkKNEGbOK6idcb5PdZDUAQDDwGAOT1FMBfAzs1mXgVh TpDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=69UPOyxx47Uw62yGDLLyCGxRX4/aVUZGqjtGeyv+o/k=; b=lLS4c/pUzcVbKCSiw2qaggotvhDhig+/o8udELZjnHVmas337GV+l3aqBh6hzjhxJN myAnEkiSTj2hC9gw13YbnLFRhUXTfFYJKBMhGqQlt9SUHr/GBPRFC9PWLxGfvtZSQlW5 krPHoZ1ETOnrBnV8gPvXrhgScBm7wQQM2zci2FrAmq0XiJPcXUiiUTNcNwSNGh29fbD3 i+oe06H8reqlcU8GuqYpTjhoTVtG4Vss2dxoRUGesxL4d5v+OyrzVPeWEyISFj2KFcMW fMxMjnslWfRGFE5/mc/9+qNgP49Yf+H/QZ9w4L4nzCr6B6dXoo2MaS9rSD8hYYPIYZLQ gGtw== X-Gm-Message-State: AA+aEWYvOvWC4DVKDmTOqVPyeirY17M5Dm7KRJMjAPPzpcs1G3Sub1+s wzqDeTaJb7P4w5liWpjiW1g= X-Google-Smtp-Source: AFSGD/UhDOelRXim3Ra3ZDe3JVjnSbEQ6w9hUaYvxXm/wWhS+ISGoNWUbLcrzqws/qwq1gnkz8/j1A== X-Received: by 2002:a19:f115:: with SMTP id p21mr421041lfh.20.1543480474848; Thu, 29 Nov 2018 00:34:34 -0800 (PST) Received: from jonathartonsmbp.lan (83-245-236-220-nat-p.elisa-mobile.fi. [83.245.236.220]) by smtp.gmail.com with ESMTPSA id h21sm190036lfk.41.2018.11.29.00.34.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Nov 2018 00:34:34 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Jonathan Morton In-Reply-To: Date: Thu, 29 Nov 2018 10:34:28 +0200 Cc: bloat Content-Transfer-Encoding: quoted-printable Message-Id: References: <65EAC6C1-4688-46B6-A575-A6C7F2C066C5@heistp.net> <38535869-BF61-4FC4-A0FB-96E91CC4F076@ifi.uio.no> <87va4gwe74.fsf@taht.net> <7125B446-F2C4-45B3-B48C-8720B1E35776@gmail.com> To: Mikael Abrahamsson X-Mailer: Apple Mail (2.3445.9.1) Subject: Re: [Bloat] incremental deployment, transport and L4S (Re: when does the CoDel part of fq_codel help in the real world?) X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2018 08:34:36 -0000 > On 29 Nov, 2018, at 10:19 am, Mikael Abrahamsson = wrote: >=20 >> I'd say the important bits are only slightly harder than doing the = same with fq_codel. >=20 > Ok, FQ_CODEL is way off to get implemented in HW. I haven't heard = anyone even discussing it. Have you (or anyone else) heard differently? I haven't heard of anyone with a specific project to do so, no. But = there are basically three components to implement: 1: Codel AQM. This shouldn't be too difficult. 2: Hashing flows into separate queues. I think this is doable if you = accept simplified memory management (eg. assuming every packet is a full = MTU for allocation purposes) and accept limited/no support for = encapsulated protocols (which simplifies locating the elements of the = 5-tuple for hashing). 3: Dequeuing packets from queues following DRR++ rules. I think this is = also doable, since it basically means managing some linked lists. It should be entirely feasible to prototype this at GigE speeds using = existing FPGA hardware. Development can then continue from there. = Overall, it's well within the capabilities of any competent HW vendor, = so long as they're genuinely interested. - Jonathan Morton