From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v3 net-next 0/9] net: Generic network resolver backend and ILA resolver Date: Mon, 11 Dec 2017 21:16:35 -0500 (EST) Message-ID: <20171211.211635.128927184437781821.davem@davemloft.net> References: <20171211203837.2540-1-tom@quantonium.net> <20171211.163416.1305681033764328226.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com, rohit@quantonium.net To: tom@quantonium.net Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:43696 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751123AbdLLCQj (ORCPT ); Mon, 11 Dec 2017 21:16:39 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Tom Herbert Date: Mon, 11 Dec 2017 14:16:17 -0800 > How can we build a system that allows an unlimited number of > resolutions without drop? IPV4 routing solves this with a prefixed trie, for example. The fundamental backing datastructure for the switching or whatever operation must be in-memory, in the kernel, scalable, and without a fronting "cache".