From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C9F893B29E for ; Thu, 23 Aug 2018 17:01:51 -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=1535058110; bh=N43Dz9KNtMDzV7kPVkzXccTl/Yh/9VdXwg6bfeFLsL8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Hz8LXnYf7DrIU1uBlWxJ9QeGe1cVcVERzG+7VjmFshvNV6IQ4dhkGlcetmnpkJJcH OCW3Yqe6q9VGpOx9GLeLy5RLchDZjuH8uZDj1hmrCcnWFWSXrqzkoW8Qrxlk94cnt3 2/q5St5zclpdm0K5tBbAC2emqskISzqF4MlNiCAjFytn/ZpkT6Q8oR7ekDF743HyP7 4UfDuRyqQ/l7vt6DL2eqdIAfxROiI9Hzye1USNQZRcn5i8owjp1/sOASQ5EfI0tkCg dA1GLsiT8gwKWTicvsmrrM26Y7UvcdqYGIWhJCbqNo268vmv9mq/ks8FWaU5e/QwtU 4Guwm3+n2Su0g== To: Dave Taht , Mikael Abrahamsson Cc: bloat In-Reply-To: References: <66e2374b-f998-b132-410e-46c9089bb06b@gmail.com> <360212B1-8411-4ED0-877A-92E59070F518@gmx.de> Date: Thu, 23 Aug 2018 23:01:50 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87a7pcbxvl.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain 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: Thu, 23 Aug 2018 21:01:52 -0000 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-route-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... -Toke