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 9B4AB236 for ; Tue, 24 Oct 2017 22:16:20 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 30B0220881; Tue, 24 Oct 2017 16:16:20 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 24 Oct 2017 16:16:20 -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=OOtsnCDtXl5iEHaHDcC3R8f2p3 e+cBUYKkdVCEIcaTQ=; b=C0daLoDGPoJkcIqwI0RPGH5g/2GOohlzV8pMCKlIqN yGiD5lqzlPlp37dQCTCJ7NXV238iHLU0lIX6VoHT2xBpvqQ2Kiyket++mrWphTTI hCukEfVOShphOtEVTMiBaHXMvQdwjCOvQ+zN69OoABWAPmWiFsAcJnd85uDL+RDW 4= 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=OOtsnC DtXl5iEHaHDcC3R8f2p3e+cBUYKkdVCEIcaTQ=; b=IVwHY1D5Xso8Ot2oDekaUi xcHdWRWuhlWWQQ1K7C9gf98f9HXtFIrPd442gLdRlswt6BuyPBq93lGZRMS4qbgs ZOMMVnGCmCG4PJ+CsY7kdgfIKYuVpXew5idFdwBiEJYPzUsmTQ+GjLJcd/H7Nlw7 YVgaSOCTeS6PcNIYbu81n4o39eJtyLCwLX4yo4HLHP49dA6HoYjXjVy11n8urY1r eOGn41R06ndCRicU08aLt0ASdnKOZStwd0q8a/Owgfs0SJI5Ldp5z7fcNEPGvwld Aifdy1/j/jApNtOPk2fuLmcQ6T7O6TLOeEXoeqdJBUZLIfnKxl04PdjEIFxscGPg == 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 CE14C246D8; Tue, 24 Oct 2017 16:16:19 -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:16:19 +0200 Message-ID: <5255654.V213Oo3rfz@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:16:20 -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 > @@ -165,6 +165,11 @@ New Features > checksums, and doesn't update checksums for output packets. > Additionally, the GSO library doesn't process IP fragmented packets. > > +* **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. > > Resolved Issues > --------------- An additional blank line is missing before the section title.