From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2001:470:dc45:1000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 831533CB59 for ; Fri, 24 Aug 2018 13:58:44 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1535133523; bh=y5FHzmoe3RX85hIALBt6fLTvTjlaw20wjSH1RmQv/8o=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ZGTnjSQe89hpuhhSziTLAwq4LYzPOR5YctTDcJKfSB9Mvv7QG3jNusc1bwEXmI5B+ PMPAyZpiMqizVn4FoN4MlUka/bKI4iRd9fDUIDFTo/vp8Z5+xme/iRbfLpBIs7Rl6c r97YEuZWcq4zy9oyBwazrfPrjOOrFNY4bKES4LZyKzMAlFAB18cNeRcRWBQmUQnvb/ pov5YCzXnGelX3iS02hQa7URQSf0HXaKQUJZUsaNsx+AraLuZU+DJ2GzJuRG7ebNdz x+YAaerKqww3UUHH0pRPGfsQpQzfaTvO+PrJQVKRQ0UqWgwh80k62bP3jrK8RTg/Le w7q7IjF5fuq8A== To: Dave Taht Cc: Mikael Abrahamsson , bloat In-Reply-To: References: <66e2374b-f998-b132-410e-46c9089bb06b@gmail.com> <360212B1-8411-4ED0-877A-92E59070F518@gmx.de> <87a7pcbxvl.fsf@toke.dk> Date: Fri, 24 Aug 2018 19:58:42 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <877ekfbq99.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Bloat] [Cerowrt-devel] beating the drum for BQL 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: Fri, 24 Aug 2018 17:58:44 -0000 Dave Taht writes: > On Thu, Aug 23, 2018 at 2:01 PM Toke H=C3=B8iland-J=C3=B8rgensen wrote: >> >> Dave Taht writes: >> >> > One of the things not readily evident in trying to scale up, is the >> > cost of even the most basic routing table lookup. A lot of good work >> > in this area landed in linux 4.1 and 4.2 (see a couple posts here: >> > https://vincent.bernat.im/en/blog/2017-performance-progression-ipv4-ro= ute-lookup-linux >> > ) >> > >> > Lookup time for even the smallest number of routes is absolutely >> > miserable for IPv6 - >> > https://vincent.bernat.im/en/blog/2017-ipv6-route-lookup-linux >> >> The IPv6 routing lookup is on par with v4 these days. We got 7.2M pkts/s >> in our XDP tests on a single core (although admittedly a fairly high-end >> Intel one). Which allows you to route 10Gbps of 64-byte packets on two >> cores... > > Call me cynical, call me grumpy... > > but did you get that result with testing 1,10,100,1000, 10,000, 100k, > 1M routes? The best > case performance on that test looked like .150us, the worst case > 1.75us Think those were single-route tests, or close to it. Don't have results handy for large routing tables for IPv6, but IPv4 performance drops by ~33% when going from a single route to a full BGP table dump... Can run some tests for v6 once by testbed is running again... -Toke