From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id BAFA6A0526; Wed, 8 Jul 2020 16:25:41 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 54E1C1DEF3; Wed, 8 Jul 2020 16:25:41 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 60C781DEF2; Wed, 8 Jul 2020 16:25:40 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id C59A15C00DB; Wed, 8 Jul 2020 10:25:39 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 08 Jul 2020 10:25:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= THawQPRFIrSp4vuOxBXegkqBeIdijvsxDurv0NCdgsU=; b=bMhc9fpLiTXMiJ73 1zktF1ekzP7vjaRvSM0k8FQLCXsi8qCVggyx7LrLmxZ8j8ZVpKQ1XPMwyyLWopLp 3MpercP5JiGSzgZlSoXPgpdH5ZQgAOXrxa+0g+BBpyMZAwrzMuJahCOGJvZnA0Vk jHM1CtD2KAdVoz/1rJD4Wc99YZsk2b/1YJ6ZDsYsS6fe5wLN55/rigcD24Z3Yq08 q5825SQU/STjnws5SDlPZyvBan2dJh4wwGjrgSYMvypzV26S4kTMktz0oKPxx+N/ d3tKvgMko5gxL6nxVdLoE/qCkOCNl0i679Jmc0+8BYs60MyfbdJ4du2AnjQP2ZOb 0eU3Eg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=THawQPRFIrSp4vuOxBXegkqBeIdijvsxDurv0NCdg sU=; b=n79CxG+B6jkxJPuPSqcgL2bIIjWeeyhsxLmmY3Glx9fY2gcRiE6zamJA9 YhmMxrL8+fiaPhO8fGtkP1mTe2p8CQp2A0EM0D3jNlzpaX/s/Zxs5sujnQ3DIi7m AB6OBYe5b6Q7Kf1qsaVXkShnr0zFiF13Qmm8cbyPB4Qrla09NPn/trsqrhNfWfRh 0FGlEinAu7EH8OzjWwX4l9fkpZeE93/GnzUXCIFe6dHfuyUIDFyt0R0/5RQxNlYY s5H4yxJCfI2anSErVE7ZOFFSN4t8wQ3Z4RY9iviR7S5LV9oZSvW3xwQgYVy6ATU1 TDxCNEHy3OWX05JYmMairSK5AYehw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudejgdejkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 37946306005F; Wed, 8 Jul 2020 10:25:38 -0400 (EDT) From: Thomas Monjalon To: "Medvedkin, Vladimir" Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com, stable@dpdk.org, bruce.richardson@intel.com, konstantin.ananyev@intel.com, david.marchand@redhat.com Date: Wed, 08 Jul 2020 16:25:37 +0200 Message-ID: <16437549.L1Hg0bpW0p@thomas> In-Reply-To: <5f0bf61b-59aa-2964-397c-e7d0f991c713@intel.com> References: <5194699.pna8TFVyyh@thomas> <5f0bf61b-59aa-2964-397c-e7d0f991c713@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: add rib and fib into the API doxygen index X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 08/07/2020 15:56, Medvedkin, Vladimir: > Hi Thomas, > > On 06/07/2020 20:31, Thomas Monjalon wrote: > > 06/07/2020 19:00, Vladimir Medvedkin: > >> Add RIB/FIB library into the API doxygen index. > >> Move LPM/LPM6 under separate section "Longest prefix match" > > [...] > >> --- a/doc/api/doxy-api-index.md > >> +++ b/doc/api/doxy-api-index.md > >> - **QoS**: > >> @@ -116,6 +114,14 @@ The public API headers are grouped by topics: > >> [scheduler] (@ref rte_sched.h), > >> [RED congestion] (@ref rte_red.h) > >> > >> +- **Longest prefix match**: > > > > I would have thought to "routing" as title of this section. > > Is "longest prefix match" better? > > I don't have any objections regarding "routing". Do you need me resend > patch? If you think "routing" is more descriptive, yes please send a v2. > >> + [LPM IPv4 route] (@ref rte_lpm.h), > >> + [LPM IPv6 route] (@ref rte_lpm6.h), > >> + [RIB IPv4] (@ref rte_rib.h), > >> + [RIB IPv6] (@ref rte_rib6.h), > >> + [FIB IPv4] (@ref rte_fib.h), > >> + [FIB IPv6] (@ref rte_fib6.h) > >> + > >> - **hashes**: > >> [hash] (@ref rte_hash.h), > >> [jhash] (@ref rte_jhash.h),