From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8714C42646; Tue, 26 Sep 2023 21:04:00 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5CD64402AA; Tue, 26 Sep 2023 21:04:00 +0200 (CEST) Received: from mail-pl1-f172.google.com (mail-pl1-f172.google.com [209.85.214.172]) by mails.dpdk.org (Postfix) with ESMTP id 03B9140269 for ; Tue, 26 Sep 2023 21:03:58 +0200 (CEST) Received: by mail-pl1-f172.google.com with SMTP id d9443c01a7336-1c3f97f2239so84755585ad.0 for ; Tue, 26 Sep 2023 12:03:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1695755038; x=1696359838; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=7fVzjNHRq9JwTAjcgtU3N/1fQfpULoJ0IM+/7WxjBfo=; b=PJOGvx7FhuHc0RM1DgdLcN/khT+ll9xO9DjeWdkNjSbQ6EA8CL2CaQ7lpEvdbNdZFu BKSEcGrTUN/GfBQBoyl9vjFcOzzx4E23DUpgPjb7ipjx6P59/+0kUT9Bw78zAU/4zWQb sIlwQQxQ0cvNE6eZwxjKQwY+Z+vz5xetXZ9xarSLfrUeEVvUymSEgFbiNJuQOJ3Lb/OR 8DwBv15DoVYNbSH6ILmoJNwNrQ2KaMa/eJhjLk4vfF7NBYQTvHB3jGAn55d/BxKpp5Ee amT3tYcKikojJDgktF5OAAecoNbiL8jefZDQlMpsrfrW5wjiGi+73hZU0zXNkT6jOfJr 8Ugw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695755038; x=1696359838; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=7fVzjNHRq9JwTAjcgtU3N/1fQfpULoJ0IM+/7WxjBfo=; b=giCsBdvKOKW4/m/o7WQ8/zF50WbG5+pv15PwyCDycWmLSXSFnMhFootBuzSUHrdKHK QN9KwNCYo+ijgxJ1mJ+vXG2ZtgC+30KcofCTkO7GspseeJ9oRpf0bsv/cAEPDYbJQH2W efKOWPRun7uDm+DxFxBrjO5FNy9egLjD/kVMGTj8jugLJEWWDhMksSMnY3TUoAZhXP8C bDt9ZLXEDoCQPikC8f8Y7d1JQqBmrlxjhRYkkC6dyfULtjT+w2GhBtM/zt12LxMmoPBD JH47NnODVP8+2uqwu3onMBbF5Hk04qz4egmwKTk6+Gmt/yD7Hl+QvOUW+F1aXA3qhUF2 M42g== X-Gm-Message-State: AOJu0YxEiOKFFfC6g2nlA5SRrLGKI9jOo4iX+gWAXzpGvbhbRLAm3pok jLKhWt/5WPXCPzmb1oNBFXkbsQ== X-Google-Smtp-Source: AGHT+IFo/6g4Zj8rMK6n2yLxIGErp7zedSDXHSCNnSfYp/fwB7LG5pqRpnjKtO6Qpp7gBQCTFUY/VA== X-Received: by 2002:a17:902:e745:b0:1c3:cee1:cc8e with SMTP id p5-20020a170902e74500b001c3cee1cc8emr11511045plf.68.1695755037958; Tue, 26 Sep 2023 12:03:57 -0700 (PDT) Received: from hermes.local (204-195-112-131.wavecable.com. [204.195.112.131]) by smtp.gmail.com with ESMTPSA id m1-20020a170902d18100b001c3f7fd1ef7sm11480404plb.12.2023.09.26.12.03.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Sep 2023 12:03:57 -0700 (PDT) Date: Tue, 26 Sep 2023 12:03:54 -0700 From: Stephen Hemminger To: yuying.zhang@intel.com Cc: dev@dpdk.org, qi.z.zhang@intel.com, jingjing.wu@intel.com, beilei.xing@intel.com, Wenjing Qiao Subject: Re: [PATCH v7 1/8] net/cpfl: add json parser for rte flow pattern rules Message-ID: <20230926120354.0f439360@hermes.local> In-Reply-To: <20230926181703.2268199-2-yuying.zhang@intel.com> References: <20230822010226.17783-1-yuying.zhang@intel.com> <20230926181703.2268199-1-yuying.zhang@intel.com> <20230926181703.2268199-2-yuying.zhang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, 26 Sep 2023 18:16:56 +0000 yuying.zhang@intel.com wrote: > From: Wenjing Qiao > > Add devargs "flow_parser" for rte flow json parser which depends > on jansson library. > > Example: > -a ca:00.0,flow_parser="refpkg.json" > > Add json parser for rte flow pattern rules which can build rules > that maps from a set of rte flow items to hardware representations. > > The cpfl PMD supports utilizing a JSON configuration file to translate > rte flow tokens into low level hardware resources. The JSON configuration > file is provided by the hardware vendor and is intended to work exclusively > with a specific P4 pipeline configuration, which must be compiled and > programmed into the hardware. > > The format of the JSON file strictly follows the internal specifications > of the hardware vendor and is not meant to be modified directly by > users. > > Signed-off-by: Wenjing Qiao It is good to see the code is now using the same JSON parser as elsewhere in DPDK. How does this interact with the P4 work done by Cristian, is this part of that? Is this treated as opaque firmware? Why is it driver specific? DPDK P4 support needs to be vendor neutral to acceptable.