From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrien Mazarguil Subject: Re: [PATCH v3 3/4] ethdev: add TTL change actions in flow API Date: Mon, 16 Apr 2018 10:12:26 +0200 Message-ID: <20180416081226.GU4957@6wind.com> References: <1522279780-34842-1-git-send-email-qi.z.zhang@intel.com> <20180416051639.188034-1-qi.z.zhang@intel.com> <20180416051639.188034-4-qi.z.zhang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Qi Zhang , "dev@dpdk.org" , "declan.doherty@intel.com" , "sugesh.chandran@intel.com" , "michael.j.glynn@intel.com" , "yu.y.liu@intel.com" , "konstantin.ananyev@intel.com" , "bruce.richardson@intel.com" , Thomas Monjalon To: Shahaf Shuler Return-path: Received: from mail-wr0-f169.google.com (mail-wr0-f169.google.com [209.85.128.169]) by dpdk.org (Postfix) with ESMTP id 9BFCB1B020 for ; Mon, 16 Apr 2018 10:12:40 +0200 (CEST) Received: by mail-wr0-f169.google.com with SMTP id d1so23281184wrj.13 for ; Mon, 16 Apr 2018 01:12:40 -0700 (PDT) Content-Disposition: inline In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Shahaf, On Mon, Apr 16, 2018 at 05:48:19AM +0000, Shahaf Shuler wrote: > Hi Qi, > > Am wondering if we can make the below more generic and not tailored for specific use cases. Regarding this, please see my previous answer [1] where I asked Qi to make his changes more focused on the use case at hand when it became clear all this work was targeting OpenFlow. The OF specification [2] defines the behavior associated with each action, for instance when a TTL is 0 or decrementing it would yield 0, the packet must be dropped. Translating this to a generic decrement action for any packet field is not so easy and not convenient. Therefore my opinion is that if OF actions as defined by this specification are supported as hardware capabilities, it makes sense to define dedicated rte_flow actions for each of them (although "OF" should be part of their name for clarity). I'll comment the patch proper in a separate message. [1] http://dpdk.org/ml/archives/dev/2018-April/096857.html [2] https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.3.0.pdf -- Adrien Mazarguil 6WIND