From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 0FF3D7EB0 for ; Thu, 26 Apr 2018 20:52:51 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A574621B51; Thu, 26 Apr 2018 14:52:50 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 26 Apr 2018 14:52:50 -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=E8PGtNKZVfElhOFGMpi/G96sDB k0GssjkyDlro2ulDQ=; b=cEvKnYdN28k7N42/J3cDvPrzlKyHbLY8Zj+yenHk14 3vWH9ktybpmNudSXEFH6P9doXcMmO9gfZPzfYr6ROhRaEwVW91RM6z8mCAyqKofX JDUtxkFmumyeAZ31KFvhYzJ47v9WwraGboG0utvk/a70NW5Ylh1DSIX/QxZ080mM s= 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=fm2; bh=E8PGtN KZVfElhOFGMpi/G96sDBk0GssjkyDlro2ulDQ=; b=JdWzAl4dNqlDwO/7cXVcHB 3CNTTSwDM2gSgLUUTiAhzcppdeKI1bpxNXUxS+QUjwwUMX1Qup+LTcT/5oAq6kvV h4IR6wLJ7Fd72pkqkYqOwOsquNV5kYv2F5eoM8UdXsJr/Zog4fsUnVEZgotQZrAB yfXjPr1AeSPB/aM0v19jS3HPTt01OiGbQy9+dauuLfkX0J1N+Jfx+tJiOepEZRoi 25df18ETkW7wo96Vk/VMIw8q4p8SVvPS8jY3mfRLG2xVWwWZlwiP2YghyX1pboGW m2mnuYVzALN2FO3z18nX61XbyypU90UBqEVy7oDDQMzu9mGFlkvqwdnpldpD9QEA == 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 03C66E47D1; Thu, 26 Apr 2018 14:52:49 -0400 (EDT) From: Thomas Monjalon To: Declan Doherty Cc: dev@dpdk.org, Ferruh Yigit Date: Thu, 26 Apr 2018 20:52:48 +0200 Message-ID: <4180955.xhS42tmOuU@xps> In-Reply-To: <20180426172919.8450-4-declan.doherty@intel.com> References: <20180426120817.6612-1-declan.doherty@intel.com> <20180426172919.8450-1-declan.doherty@intel.com> <20180426172919.8450-4-declan.doherty@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v7 3/4] ethdev: add mark flow item to rte_flow_item_types 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: Thu, 26 Apr 2018 18:52:51 -0000 26/04/2018 19:29, Declan Doherty: > Introduces a new action type RTE_FLOW_ITEM_TYPE_MARK which enables > flow patterns to specify arbitrary integer values to match aginst > set by the RTE_FLOW_ACTION_TYPE_MARK action in previously matched > flows. In the title, I don't think you need specify rte_flow_item_types (which doesn't exist BTW). I suggest: ethdev: add mark flow item