From nobody Fri Jul 22 09:56:14 2022 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Lq4Zz0cMvz4WqYk for ; Fri, 22 Jul 2022 09:56:27 +0000 (UTC) (envelope-from SRS0=9Ir/z3=X3=codenetworks.net=sm@eigbox.net) Received: from bosmailout09.eigbox.net (bosmailout09.eigbox.net [66.96.189.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Lq4Zy25rSz3sNP; Fri, 22 Jul 2022 09:56:26 +0000 (UTC) (envelope-from SRS0=9Ir/z3=X3=codenetworks.net=sm@eigbox.net) Received: from bosmailscan02.eigbox.net ([10.20.15.2]) by bosmailout09.eigbox.net with esmtp (Exim) id 1oEpOT-0008By-6t; Fri, 22 Jul 2022 05:56:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=codenetworks.net; s=dkim; h=Sender:Content-Transfer-Encoding:Content-Type: In-Reply-To:Subject:From:References:Cc:To:MIME-Version:Date:Message-ID: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=TMnpSNmHTUc2UO86c/HeuQEjGXrcCw/slHIpneJiY+c=; b=hLJoFdAIfJpiKeH9CP3+5VO6Yn fXn21NqmwBka82NzoU5iRkeLlaAZpBM772MzpU9pCCpxU1FV1ap8rNHRo4UosdlacEuFj+PomCLhR HfKVM9ps3vybp5J7YmyPlC5zBGvlsXVdd8ufS6LjRGLmmDK/oyq4duVK14F8p3wV6GP8CH60H0GKN pjHGAYVGTAs5ZICZkXTVWbq6xNi2vUUqmAKX/nv49rlXjJ1N6UkauUzWHkVlNcgWvb6wyqZgPyxu3 JEz8J5YB8B0U6k79KJIWlArCnO0tb9jDiLcQBLvSYxjNwy2n/5DXB6NPBq0E16IyTMrZLePqLdKHo Va2cU+bw==; Received: from [10.115.3.32] (helo=bosimpout12) by bosmailscan02.eigbox.net with esmtp (Exim) id 1oEpOR-0007I0-Lx; Fri, 22 Jul 2022 05:56:23 -0400 Received: from bosauthsmtp09.yourhostingaccount.com ([10.20.18.9]) by bosimpout12 with id y9wK270050BkY8i019wNBk; Fri, 22 Jul 2022 05:56:23 -0400 X-Authority-Analysis: v=2.3 cv=d4VuNSrE c=1 sm=1 tr=0 a=+tcVrJynzLVJ9yqDAOBWjQ==:117 a=Ek/qOh1uPkKSHvd30yk7rg==:17 a=oZrnjGktn3rzEU8X:21 a=IkcTkHD0fZMA:10 a=RgO8CyIxsXoA:10 a=-Yl_685HdVUA:10 a=4wtJTTcTZKfIjyBIvQgA:9 a=QEXdDO2ut3YA:10 a=n_7y49_PyBNFoLxfVjzj:22 Received: from cm-81-9-194-73.telecable.es ([81.9.194.73]:26174 helo=[192.168.3.100]) by bosauthsmtp09.eigbox.net with esmtpa (Exim) id 1oEpON-0006qJ-3y; Fri, 22 Jul 2022 05:56:19 -0400 Message-ID: <40f829a2-51c4-e993-e70e-ca8be1a0d3d8@codenetworks.net> Date: Fri, 22 Jul 2022 11:56:14 +0200 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Content-Language: en-US To: sthaug@nethelp.no, lutz@donnerhacke.de Cc: nc@FreeBSD.org, freebsd-net@FreeBSD.org References: <20220721161647.GA7879@belenus.iks-jena.de> <20220721.193816.806320685105925842.sthaug@nethelp.no> From: Santiago Martinez Subject: Re: How does FreeBSD expect to compete in a DPDK/VPP world? In-Reply-To: <20220721.193816.806320685105925842.sthaug@nethelp.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-EN-UserInfo: d3bdfab0736480cedf04ed92aaea2ef5:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: sm@codenetworks.net X-EN-OrigIP: 81.9.194.73 X-EN-OrigHost: cm-81-9-194-73.telecable.es X-Rspamd-Queue-Id: 4Lq4Zy25rSz3sNP X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none ("invalid DKIM record") header.d=codenetworks.net header.s=dkim header.b=hLJoFdAI; dmarc=none; spf=pass (mx1.freebsd.org: domain of "SRS0=9Ir/z3=X3=codenetworks.net=sm@eigbox.net" designates 66.96.189.9 as permitted sender) smtp.mailfrom="SRS0=9Ir/z3=X3=codenetworks.net=sm@eigbox.net" X-Spamd-Result: default: False [-2.00 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-0.997]; FORGED_SENDER(0.30)[sm@codenetworks.net,SRS0=9Ir/z3=X3=codenetworks.net=sm@eigbox.net]; R_SPF_ALLOW(-0.20)[+ip4:66.96.128.0/18]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_NONE(0.00)[66.96.189.9:from]; ASN(0.00)[asn:29873, ipnet:66.96.128.0/18, country:US]; R_DKIM_PERMFAIL(0.00)[codenetworks.net:s=dkim]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.96.189.9:from]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[sm@codenetworks.net,SRS0=9Ir/z3=X3=codenetworks.net=sm@eigbox.net]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RCVD_VIA_SMTP_AUTH(0.00)[]; DKIM_TRACE(0.00)[codenetworks.net:~]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[codenetworks.net: no valid DMARC record]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N I think there is a mix of things here. For the VXLAN or MPLS this depends on the role of BSD. For DC with leaf and spine deployment, nowadays VXLAN is good enough, as we can terminate the VXLAN on FreeBSD + Bhyve. Now if you are in a transport network or need to terminate services (L2VPN, L3VPN, VPLS ,EVPNoMPLS) then MPLS and SR-MPLS are required for the data-plane and RSVP, BGP-LU and ISIS/OSPF with SR extension for the control plane. Some networks are still running LDP but nobody will deploy a greenfield on or a modern network on it. On the DKDP and VPP, the intention is to bypass the kernel, so i don't see why FreeBSD itself should come with a solution for that apart from making sure DPDK and VPP work on FreeBSD. The last time i spoke with somebody from Intel, the response was that DPDK was is good shape (For FreeBSD), but also I remember some email on this list saying that some things are missing. Not sure what the current status for VPP. Regards. Santi On 7/21/22 19:38, sthaug@nethelp.no wrote: >>> Not that I work at an ISP or tech company in a networking role, I don't. >>> Heck, adding even MPLS support has been on my bucket list for a while, but >>> am too lazy to get started. I do want to move to a networking-based role at >>> $DAYJOB, but we'll see about that. >> MPLS is outdated (performance-wise) and (functionally) replaced by vxLan, or >> do I miss something? > No idea what you mean by outdated (performance-wise). Yes, I know the > initial claims for MPLS touted faster packet switching times - but > that hasn't been relevant for many years. > > MPLS is about functionality. Yes, there is some functionality overlap > with VXLAN - but the overlap is certainly not complete. Personally, > I'd love to see an MPLS implementation in FreeBSD. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no >