From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 3F90B42B72
	for <public@inbox.dpdk.org>; Mon, 22 May 2023 16:05:57 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 1CB7240EE7;
	Mon, 22 May 2023 16:05:56 +0200 (CEST)
Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com
 [209.85.208.178])
 by mails.dpdk.org (Postfix) with ESMTP id 250D340EE5
 for <users@dpdk.org>; Mon, 22 May 2023 16:05:54 +0200 (CEST)
Received: by mail-lj1-f178.google.com with SMTP id
 38308e7fff4ca-2af2958db45so35358711fa.1
 for <users@dpdk.org>; Mon, 22 May 2023 07:05:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1684764353; x=1687356353;
 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=LZRRc+prty6h4ysCJ3EtuD5FaMj92YjhG1o6Hdy8UcI=;
 b=oYaR2dcKCoi4Rbadsj0MDRWmDo7WTB59/J/poafo0DOXze2A3mWLBsm0izjUhf9KPH
 OnYxUOhLWhLf7LSm+3DYliQwlWJiRV+hnOrHH3pHYV7RPESpq4oNZiiEihpuziR2u6Lq
 /IWaf3LmxsopDdyturWrRBebMvKGLFexvfAKKVkZjJWWek01DXv5ZoCFVEY5/ZFrGGaS
 12L6X7TklFPUAPk2OWSwt1y0bNUqiaBAYXKE6+ZcQBy6P8IfuIguSMRS0ulAS0otZoBZ
 48Zj4Fp+gRzWjWCU407QMos+HA7FT85mf2P1IW42NbhhXOpJbrw/1D/nhCtAMh6snxdU
 Egpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1684764353; x=1687356353;
 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=LZRRc+prty6h4ysCJ3EtuD5FaMj92YjhG1o6Hdy8UcI=;
 b=jl0I11tvebdT9m5UxwW8CchnJgF78RTRcM2HQNC3ubVPfRCIN9o+g5XS02anFR06Cs
 MES6/XHHy0zfCVpT8xEBEKJJgH0hTMtnAvqrogLkkSS/TdT97ia4p4aPXS0paU9yQa4q
 Emd0YVjAbi63/z2+QilnQk7Gmcid5VULpTSz+0mKAa22m2/TWtVSnb8C4dsS6kstnIxx
 enHGxdJdw1fl3Ah6y08Sc9XF1zPVbM/psT7z+PJtyfT2+r+PBaPRHIySEHSzGwGAwv1D
 mnIEkLyXdVwvpwWtLf73UxHVIf9IR+GiQqhq0o/2buqHXtugyJB5dS6B8WKguwmfCFbJ
 wZLQ==
X-Gm-Message-State: AC+VfDxnBuPGV8kyr9/VPorR7+XzRxK1jv2rwdwCLKuhGypDNZVcaiy1
 UQqIcjHstyPetg9Z2yfdagdese0OtHs=
X-Google-Smtp-Source: ACHHUZ5om0YH4VefMPnlnMx1ns7CWIzdwL+hKJhZoQYvMfhOuYU78rHrib+WqApkD+rng8wXtV+WTA==
X-Received: by 2002:a2e:a3c5:0:b0:2ab:42c7:cf25 with SMTP id
 w5-20020a2ea3c5000000b002ab42c7cf25mr3640533lje.13.1684764353165; 
 Mon, 22 May 2023 07:05:53 -0700 (PDT)
Received: from sovereign (broadband-109-173-110-33.ip.moscow.rt.ru.
 [109.173.110.33]) by smtp.gmail.com with ESMTPSA id
 a20-20020a2eb174000000b002ad8174d025sm1145669ljm.122.2023.05.22.07.05.51
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Mon, 22 May 2023 07:05:52 -0700 (PDT)
Date: Mon, 22 May 2023 17:05:50 +0300
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Aisenur =?UTF-8?B?WW9sZGHFnw==?= <aisenur.yoldas@b-ulltech.com>
Cc: users@dpdk.org
Subject: Re: Rte_flow function
Message-ID: <20230522170550.630a0c3c@sovereign>
In-Reply-To: <1989053041.4731986.1684762501124.JavaMail.zimbra@b-ulltech.com>
References: <1989053041.4731986.1684762501124.JavaMail.zimbra@b-ulltech.com>
X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
MIME-Version: 1.0
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 <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org

2023-05-22 16:35 (UTC+0300), Aisenur Yolda=C5=9F:
> I am trying to use the rte_flow_query function to find all the flow rules=
 in a port, but when it comes the action parameter i cannot find the right =
way because when I use count action like in the ipsec example
> =C2=A0
> [...]
> =C2=A0
> What is the correct way to use this function in order to reach all the fl=
ows of the port.

There is no API to query the list of flow rules of a port.

rte_flow_query() is to query the state a specific single flow rule.
For example, if the action list on flow rule creation included COUNT,
then rte_flow_query() would allow to get the counter value
(how many packets have hit the rule).
Your action list doesn't have a COUNT action (or any stateful action)
so there is nothing to query.