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 71185429F9 for ; Wed, 26 Apr 2023 07:48:06 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E30C8410DC; Wed, 26 Apr 2023 07:48:05 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 11A8A40DDA for ; Wed, 26 Apr 2023 07:48:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1682488083; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Oj3DobsojlKstR59rzzzFAI/1IADO2pPq++/Qkjx95A=; b=XPF2nFiAGZGYhuMzde0Ibwm1flvCcDyFJQ3kiRELrspj+hlV1D9yekp7BsUe++kDvfs21M 8Y7aNVRHX3S+MyG3HPY7r3eDlVz2qUZ30tQg5noyVhwu2dX0S5vbj1GUushzEsifb+vGGv qXVt3wEjWcPJ1uFneLigjXxTRmxCxa4= Received: from mail-pf1-f197.google.com (mail-pf1-f197.google.com [209.85.210.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-602-wfj7_SrbPkG_pnf8q7BG6w-1; Wed, 26 Apr 2023 01:48:01 -0400 X-MC-Unique: wfj7_SrbPkG_pnf8q7BG6w-1 Received: by mail-pf1-f197.google.com with SMTP id d2e1a72fcca58-63b5c830d77so4563778b3a.1 for ; Tue, 25 Apr 2023 22:48:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682488080; x=1685080080; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Oj3DobsojlKstR59rzzzFAI/1IADO2pPq++/Qkjx95A=; b=AFsYXnKZY7CGMgF1/LZ3eJ2YaQfNcmAQ2e56K3mX5SadlZKgVW1SCKM11YQTvnq4ZI CQzlSHTX9ObTPeCmTdB/L1iACOPvbuSPIOhzqduOZcKe0g7BSB1yjbXRY07Q/D+ZQGPy VCFbRqy6/rkcQFhv83wEV3YS7T5PXc8VzlxftErLVQULT4PsSuSkWwYg9MBo/izchTlP HjuTziug3yIhrZWQfLu1Q2bJSrDpVA9uAHzkIBOtSAjwT5ROiI6NenMud0hYFTI67fE9 +xoWWu5fTKQ3/gkYoHWtpHIgVOzbueolZosq4xty4SoG4+QV15Wzx+Cljo2CnbpP3Cxc 9c6A== X-Gm-Message-State: AAQBX9fgNxPxqRXax3nlGPxVMKCg8X61Qw6rg3UI+bPFhrVEu/pKvP6A TOMzbkO6BUMyk0GFJkmVdAnCwUfyK8S0N5PIwBD465U8AhxrGEO2LUdRrclK0AVkFSuoN9dvOa3 x9vRIWcSXAjnKFHeZxjeHdg== X-Received: by 2002:a05:6a00:15c9:b0:63b:854e:8459 with SMTP id o9-20020a056a0015c900b0063b854e8459mr29320211pfu.31.1682488080669; Tue, 25 Apr 2023 22:48:00 -0700 (PDT) X-Google-Smtp-Source: AKy350blSdOObn4WFseX87em5Qv+o9sbI9UlSH9JNkfU8McJNHiJ70Joai0Q8Aj1jaqIFN2l3ufbOHHrl6v8gN2/iuw= X-Received: by 2002:a05:6a00:15c9:b0:63b:854e:8459 with SMTP id o9-20020a056a0015c900b0063b854e8459mr29320200pfu.31.1682488080396; Tue, 25 Apr 2023 22:48:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 26 Apr 2023 07:47:49 +0200 Message-ID: Subject: Re: Generic flow string parser To: Cliff Burdick Cc: users , Thomas Monjalon , Ori Kam X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Wed, Apr 26, 2023 at 6:47=E2=80=AFAM Cliff Burdick = wrote: > > Does anyone know if a generic parser for flow strings exists anywhere? Th= e one inside of testpmd is ideal, but unfortunately it's self-contained and= not distributed as part of a normal DPDK install. This seems like somethin= g that is likely reinvented over and over and it would be useful if there w= as a single API to take in strings and generate flows. I heard this same question in the past, but I don't remember the answer. Copying Thomas and Ori who might know. --=20 David Marchand