From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id E45821B7E4 for ; Tue, 24 Oct 2017 22:18:43 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4EFC920E45; Tue, 24 Oct 2017 16:18:43 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 24 Oct 2017 16:18:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=wLSRlfiYg7rr/JocOCQl2JmgTz C3WpohMdpyA0iQCIc=; b=h8Sge0xKLsrqdYyV6R+ui7nZpxVWLHhAIJmM5HSrFq bnhA+U3EF2iIrqdhj8f4on8S3YWoCpnzaHK6ohFZEtQ+PojOLCaGBvYgt6An2wkN siaCQMi7yVzbEum5rpvqGJjSB2EnGuUHOPxDohbvmf+OVTpmLxEQJ1tY/MyWW3kL Y= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=wLSRlf iYg7rr/JocOCQl2JmgTzC3WpohMdpyA0iQCIc=; b=ZJHH1EGN0b8cdltDKVMEBs RW3oXfjRKyxxQMWYFP6TPUlSMWrxAQP7optaAt+alPP8Kn5BACA56howacUPeEwq 9Kopp0wlMJyOOS948rHJMZVh8PvrinAiAAfCkrASI2M2mpx5A2uQGRrduMkfHiU5 Tux1imte7rJWAuhJxDAL+B53NCx+jviUnkF+smYRm0CVIeV/sM1KKXS+FxwzJxn7 FwNLshRcjt13d5QIrTceb/ncTeoVz3+dfKz73PP0IYu1cH/SdneLlwsh45gFeu74 5am/HrtE8bFRmhdYUhQ1v6yg7dl7nVAwpDkDESjGItqM29t7W0yUmMP5CVbILeew == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id DB7A57F94D; Tue, 24 Oct 2017 16:18:42 -0400 (EDT) From: Thomas Monjalon To: Bernard Iremonger Cc: dev@dpdk.org, ferruh.yigit@intel.com, konstantin.ananyev@intel.com, cristian.dumitrescu@intel.com, adrien.mazarguil@6wind.com, jasvinder.singh@intel.com Date: Tue, 24 Oct 2017 22:18:42 +0200 Message-ID: <3340017.Z97XVWggdc@xps> In-Reply-To: <1508866083-15646-2-git-send-email-bernard.iremonger@intel.com> References: <1508771778-617-1-git-send-email-bernard.iremonger@intel.com> <1508866083-15646-2-git-send-email-bernard.iremonger@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v11 1/4] flow_classify: add flow classify library 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: , X-List-Received-Date: Tue, 24 Oct 2017 20:18:44 -0000 24/10/2017 19:28, Bernard Iremonger: > --- a/doc/guides/rel_notes/release_17_11.rst > +++ b/doc/guides/rel_notes/release_17_11.rst > +* **Added the Flow Classification Library.** > + > + Added the Flow Classification library, it provides an API for DPDK > + applications to classify an input packet by matching it against a set of flow > + rules. It uses the librte_table API to manage the flow rules. The library must be added to the list in the release notes: + librte_flow_classify.so.1