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 E8E3EA329E for ; Thu, 24 Oct 2019 00:05:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1505F1C1C8; Thu, 24 Oct 2019 00:05:00 +0200 (CEST) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by dpdk.org (Postfix) with ESMTP id B5EBB1C1C6 for ; Thu, 24 Oct 2019 00:04:58 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id E1F4B67B7; Wed, 23 Oct 2019 18:04:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 23 Oct 2019 18:04:57 -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=mesmtp; bh=QYSCyHqxMipkg9zywXPYFtK11BhvKJSjzQIKTK0Ql0s=; b=OSQi/dBJ5xA8 QPbu9g3ltTEQe8o/atsoATq6cff9hWogAtQt2NuvObW2m3fPLUXxf5ArDymsE/aG /Yb7ZqnD7wYpftCUHANi4g6I/5mMMF07SxhojoTpL77RE8eNUR7CdLBUglqSmqr+ iMpiRvRtFbF2SxuyoaJOhAGG5Pz1vvA= 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=fm1; bh=QYSCyHqxMipkg9zywXPYFtK11BhvKJSjzQIKTK0Ql 0s=; b=KMegzQ7+/h1hG/TlaDjkwLjSukQwhfp6F+pdoOIjqlhbseA7NNiIoXEVg O2HqhOMXXsp70ffNNp4NjTTY8xJVlHf4kEgYouz6njUs8/qM2e9XRVqUPom19nDu ZVkhvQEaZcN8ypHmS6SgMqUwo3LVaSbZFpiPv0Bzt9TfR2rnIzfFZ+ybGSfLddZn vJw6qqONYi6wE+OU4lBFFntG0U2oUmyLAXted8vE3wc8/8QjG1DOgJyOUH8XWVOQ QFqkmS7UglKbf0yPEELBqbS98PROjmVlBoxHChk38Q2Wis8qCy3Y4BuBtmI2bJM6 ofXDSaOSqyd9OAn/P2Axt6Re5bdhw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrledtgddtfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 D541780060; Wed, 23 Oct 2019 18:04:55 -0400 (EDT) From: Thomas Monjalon To: kirankumark@marvell.com Cc: dev@dpdk.org, Adrien Mazarguil , Wenzhuo Lu , Jingjing Wu , Bernard Iremonger , John McNamara , Marko Kovacevic , Ferruh Yigit , Andrew Rybchenko , Olivier Matz , ajit.khaparde@broadcom.com Date: Thu, 24 Oct 2019 00:04:54 +0200 Message-ID: <2495846.fSxBg5hd9C@xps> In-Reply-To: <20191022041648.4812-1-kirankumark@marvell.com> References: <20191021091617.11290-1-kirankumark@marvell.com> <20191022041648.4812-1-kirankumark@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v10] ethdev: add HIGIG2 key field to flow API 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" 22/10/2019 06:16, kirankumark@marvell.com: > --- a/doc/api/doxy-api-index.md > +++ b/doc/api/doxy-api-index.md > @@ -101,7 +101,8 @@ The public API headers are grouped by topics: > [GSO] (@ref rte_gso.h), > [frag/reass] (@ref rte_ip_frag.h), > [LPM IPv4 route] (@ref rte_lpm.h), > - [LPM IPv6 route] (@ref rte_lpm6.h) > + [LPM IPv6 route] (@ref rte_lpm6.h), > + [HIGIG] (@ref rte_higig.h) Sorry, my comment is a bit late, but I would prefer to see HIGIG earlier in this list. You say it is a protocol at layer 2.5, so it should be listed probably close to ICMP. What is your opinion?