From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 629713CB36 for ; Tue, 16 Oct 2018 11:06:32 -0400 (EDT) Received: by mail-pl1-x62a.google.com with SMTP id q19-v6so8089782pll.5 for ; Tue, 16 Oct 2018 08:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Vp4Bbkvy6IWZy1ofYzKob6eePzISKKDD+Zga/gKk19c=; b=G1qOYt+xrb4YYVLwOtgK6BAo64tblpztHuEwqhmMOjOiFNKS4WH903BEPXWe3jpeQE 5tXS7dILWmOHIS8MJ3q+Ac7E/FjbiUklkWnDCUNzF8mAwbK6RQC3tKacJEHAn5YzXz5g ZES49sIonHov1YH3Z0ESfyEnk97SMzLthRNWB7aljFhkdvCkS8JL5JzpgcPSzQVNnr7E Krb/YSJBETfDBTLskCBxZoMZsON1gCf/o+AWNcyq2/Pkn47NCiJIJ+ASWKy6JDZig+Dl jOaWslrY+ApdQIYI7UajLrczaSOYuoUziG+MppXUelkOTRiGogbVsOcf2wfyf/dnZIZ5 RyvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Vp4Bbkvy6IWZy1ofYzKob6eePzISKKDD+Zga/gKk19c=; b=p2DgrxOzy9cL40QSIcUqC+LMGrhtTZlscEG4fvmyW0yo1Gner5GMv2cdPnCV4hcED7 cvYe0LRo1nj89OmnZbBZKsWQh70iWEObIJ6A81ia3X2isRqo0rxy3zZO5Rzl76hNVzHv /+jpTBBbYdWi87HmFZapWtskhA3hG8rLknSeqZLUu7WJ0zzQMYoFWLE9pxwmYD/QzXIE 4cjwb7M6w3WCmYmPple+oZLpOIrP29UI3uGjJwGJ+QDHCQZkMCyWkwODXEeuxXV8Y3rP iJ7DQBJ38sF3b8ln0CkBiDpMK/d3eSbI/QWxQhBU2vYGFg2mmXDOU+Ux8ot50sTgpZ0I 9cKw== X-Gm-Message-State: ABuFfohMp2HLDgP1lCVIiIhxUsBmGlxmaNEDhG5YgJlDkU/nkWaxQSjZ PO0skNvy5XV1kvTXZlVGzEgNnQ== X-Google-Smtp-Source: ACcGV62bLfmIXccH/uta8j/qW6ou2Ds46+kRqcBWORWmTQ3+iRqUHkHO8qiziOuMXETQ1VVpaimwOQ== X-Received: by 2002:a17:902:33c2:: with SMTP id b60-v6mr21916344plc.105.1539702391363; Tue, 16 Oct 2018 08:06:31 -0700 (PDT) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id 189-v6sm17579276pfe.121.2018.10.16.08.06.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 16 Oct 2018 08:06:31 -0700 (PDT) Date: Tue, 16 Oct 2018 08:06:28 -0700 From: Stephen Hemminger To: Stefan Alfredsson Cc: Message-ID: <20181016080628.2ca3652b@xeon-e3> In-Reply-To: <68031ed5-05e5-8f53-5e7d-ef0fce9d08da@kau.se> References: <68031ed5-05e5-8f53-5e7d-ef0fce9d08da@kau.se> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Bloat] vyatta in AT&T 5G gear 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: Tue, 16 Oct 2018 15:06:32 -0000 On Tue, 16 Oct 2018 11:59:18 +0200 Stefan Alfredsson wrote: > On 2018-10-16 11:31, Mikael Abrahamsson wrote: > > > On Mon, 15 Oct 2018, Dave Taht wrote: > > > >> Vyos (the open source fork of vyatta) was one of the first to add > >> fq_codel support... I wonder.... > >> > >> http://linuxgizmos.com/att-releases-white-box-spec-for-its-linux-based-5g-routers/ > >> > > > > Isn't Vyos just running the Linux kernel for forwarding? So they > > received fq_codel for free when the Linux kernel got support for it? > > They just had to make it configurable? > > > > Yes, according to this blog post, > http://www.five-ten-sg.com/mapper/blog/Bufferbloat%20solved%20with%20Vyos > > "Now that Vyos "helium" is available with a Linux 3.13 kernel, the > fq_codel queueing discipline can be used to solve many bufferbloat > issues. The nightly "lithium" builds contain my patches that allow > fq_codel to be used via the native Vyos configuration system." > > Anyway it's nice to see the Vyatta heritage living on in it's various > forms (the AT&T "production hardened" Vyatta, to the Ubiquity EdgeMax > and some UniFi devices, to the VyOS open version and now the future > plans with dNOS -> DANOS. > > /Stefan > > > There are two basic components to network OS, the control plane and the data plane. VyOs has the old V1 which is filesystem based control plane and kernel dataplane. DaNoS has yang/netconf database based control plane (in Go) and DPDK (or switch offload?) based dataplane. Ubiquity redid the control plane as well, and uses their own hardware for dataplane. So more of "my grandfather's ax"...