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 8EE0C4618E for ; Tue, 4 Feb 2025 16:50:31 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 81473410E4; Tue, 4 Feb 2025 16:50:31 +0100 (CET) Received: from mail-yb1-f173.google.com (mail-yb1-f173.google.com [209.85.219.173]) by mails.dpdk.org (Postfix) with ESMTP id 2469F400D6 for ; Tue, 4 Feb 2025 16:50:30 +0100 (CET) Received: by mail-yb1-f173.google.com with SMTP id 3f1490d57ef6-e5ae3fc15acso3262141276.0 for ; Tue, 04 Feb 2025 07:50:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738684229; x=1739289029; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NXKCyX5KO6hM3Mq2GAbzYMacOYkbfyxkPSxQ3EOyFBA=; b=cGYjHbE9UIfk4cwclZoxzcLQPKdBCSa/jmWIefNnMf0xOaT99wOAW+DwftBZsNHNF8 Mn2+RA5e8bbEZKR0YKDen8fzlbZcmP5qH8VUKI6KQLvYGiETlW5V5QHAVwoJZvIUXiHD /Yefw3ds5b00jeYon3TNZBkm9KcrHdj5MGoaqkHYr/gr62zig8mA647N9pEGbwip3J07 W18WF4/cWml6a3x5qkxdJ00Ui07P4p5Z0WE1TWpkfo5clZZnTxmiw/HVfktqi7Lut17C dhdyQiDiMznoqFXS+tPFq2ERT7LnZ5S46Yt1HSEjHgZWTtAkN03w4hxTUKLBr2ZRj9ry SOXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738684229; x=1739289029; h=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=NXKCyX5KO6hM3Mq2GAbzYMacOYkbfyxkPSxQ3EOyFBA=; b=UJQftZM1tBZK5iEtGNydOvpYzZg5/rtIL+LBo+AEQc3TV8bpGlZhnAbmEiavW6xI0a yIQipK9DShD7d5ag3wwc+uO20Ex1EdlY7o6FImNuE9N51j6nhnVwFkxA4/75Gf3WamS2 Ni5aUPteFK4QwBkS79Gshkzac5L7qtmG7Yk97HNGJeQTSIfLTvJMn+U0MqYdBlDnke+Q SG08JNAc4BT02T0U0pJ3a8Kz9AGfDm4+B50zxMVsQCkl5atGwbOC+WE4H1h8c7wvjDzC /lURvRU2i9a3Mbw8xtmMfd9jmIB8og38ABNlF4DMZJh23mDNorQp7e92F3CUJPePLpZJ nJkw== X-Forwarded-Encrypted: i=1; AJvYcCUTon/qoZK5+YA97rCNblBT/pK5/2TiZFLz5dKwTUPgAK1ofaBzK+/AYSY96fcPcDPyW2U6VA==@dpdk.org X-Gm-Message-State: AOJu0YxwJumxG2c4WWW6TWiPyGXPO03aOgUqrYJcu2PaSddYVZx3i542 4hllKrwIONJWbgkQWlfmNbpJ6HDBR1MMNh+oqDpvndA5pjrRo4vxtY32X12Zulgv8nJfxsI99ju Vprslbp4iy4T12zIqmrtEzetSwDA= X-Gm-Gg: ASbGncuS4dCJrW5OPetxIwIcMyg2YFJWyU/tczrJdqcKoR+xe/hlsnFKtiQRpZ46Oap r1nNMK8e8fYvyiQg4qirHvD/ma2p6OQ2SlpCjsiNsCqFL3UqkmauW3hExUenE7HSnthSyFfU= X-Google-Smtp-Source: AGHT+IHjOdz9Zf7Scq/PmFI8q8BJt3xdWvRbbEWzPSmpfRNbDInlMfmA1kzS5iKZclGkyoZgZsyy6HO+BBTsjVeKE64= X-Received: by 2002:a05:690c:6c0e:b0:6f9:8212:877a with SMTP id 00721157ae682-6f982128951mr12010377b3.8.1738684229409; Tue, 04 Feb 2025 07:50:29 -0800 (PST) MIME-Version: 1.0 References: <20250128214616.3f9324de@sovereign> <20250203180007.2c5e0607@sovereign> <2a89c290-48c8-497a-82d8-6a9a8bc5887b@intel.com> In-Reply-To: <2a89c290-48c8-497a-82d8-6a9a8bc5887b@intel.com> From: Sid ali cherrati Date: Tue, 4 Feb 2025 16:50:18 +0100 X-Gm-Features: AWEUYZkgxuptF190u_XgivdjdCeHl4YZs8FMyqUSnwfCOG1ONU73IizJuuYklLk Message-ID: Subject: Re: DPDK Flow Filtering Not Working as Expected To: "Medvedkin, Vladimir" Cc: Dariusz Sosnowski , Dmitry Kozlyuk , Anatoly Burakov , "users@dpdk.org" Content-Type: multipart/alternative; boundary="000000000000dee4a5062d52f79f" 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 --000000000000dee4a5062d52f79f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Vladimir, Thank you for the clarification. I'll try using the E810 and provide an update on the issue. Best regards, Ali Le mar. 4 f=C3=A9vr. 2025 =C3=A0 16:41, Medvedkin, Vladimir < vladimir.medvedkin@intel.com> a =C3=A9crit : > Hi all, > > The goal that Ali is trying to achieve is not possible with the X540-AT2 > NIC (as with any other ixgbe NIC). The problem is related to: > > 1. The first rule is processed by the FDIR engine > > 2. FDIR engine is executed in the HW pipeline almost in the end (just > before RSS), i.e. after other filters that we could use to match all > other packets (5tuple filter engine in this particular case). > > Therefore my recommendations here would be to use a modern NIC such as > E810 to implement the required filtering logic. > > On 04/02/2025 09:28, Dariusz Sosnowski wrote: > > Hi, > > > > Anatoly, Vladimir - Would you be able to help with the issue regarding > DROP action not being supported on X540-AT2? > > > > Best regards, > > Dariusz Sosnowski > > > >> From: Sid ali cherrati > >> Sent: Monday, February 3, 2025 18:12 > >> To: Dmitry Kozlyuk > >> Cc: users@dpdk.org > >> Subject: Re: DPDK Flow Filtering Not Working as Expected > >> > >> External email: Use caution opening links or attachments > >> > >> Here is a better version of the code : > >> > > >> > >> Le lun. 3 f=C3=A9vr. 2025 =C3=A0 16:00, Dmitry Kozlyuk dmitry.kozliuk@gmail.com> a =C3=A9crit : > >> 2025-02-03 14:51 (UTC+0100), Sid ali cherrati: > >>> [...] > >>> if (!rte_flow_validate(port_id, &attr, pattern, actions, &error)){ > >>> flow =3D rte_flow_create(port_id, &attr, pattern, actions, &error); > >>> } > >>> > >>> if(flow !=3D 0){ > >>> printf("Filed to create drop flow filter \n"); > >>> return -1; > >>> } > >>> [...] > >>> The issue is that when I implement this, I get an error on the drop > filter: > >>> "Failed to create rule." Do you have any idea why this might be > happening? > >> There is no this exact error text in your code or DPDK, > >> I assume we're talking about the quoted fragment. > >> `flow` is a pointer, the correct error condition is `if (flow =3D=3D N= ULL)`, > >> so your code probably misinterprets success as error. > >> Also `flow` is not assigned if `rte_flow_validate()` returns non-0. > > -- > Regards, > Vladimir > > --000000000000dee4a5062d52f79f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello Vladimir,

Thank you for th= e clarification.

I'll try using the E810 and provide an update on= the issue.

Best regards,
Ali


Le=C2=A0mar= . 4 f=C3=A9vr. 2025 =C3=A0=C2=A016:41, Medvedkin, Vladimir <vladimir.medvedkin@intel.com> a = =C3=A9crit=C2=A0:
scherrati1@gmail.com>
>> Sent: Monday, February 3, 2025 18:12
>> To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
>> Cc: users@dpdk= .org
>> Subject: Re: DPDK Flow Filtering Not Working as Expected
>>
>> External email: Use caution opening links or attachments
>>
>> Here is a better version of the code :
>>
<snip>
>>
>> Le lun. 3 f=C3=A9vr. 2025 =C3=A0 16:00, Dmitry Kozlyuk <mailto:= dmitry.kozliu= k@gmail.com> a =C3=A9crit :
>> 2025-02-03 14:51 (UTC+0100), Sid ali cherrati:
>>> [...]
>>> if (!rte_flow_validate(port_id, &attr, pattern, actions, &= amp;error)){
>>> flow =3D rte_flow_create(port_id, &attr, pattern, actions,= &error);
>>> }
>>>
>>> if(flow !=3D 0){
>>> printf("Filed to create drop flow filter \n");
>>> return -1;
>>> }
>>> [...]
>>> The issue is that when I implement this, I get an error on the= drop filter:
>>> "Failed to create rule." Do you have any idea why th= is might be happening?
>> There is no this exact error text in your code or DPDK,
>> I assume we're talking about the quoted fragment.
>> `flow` is a pointer, the correct error condition is `if (flow =3D= =3D NULL)`,
>> so your code probably misinterprets success as error.
>> Also `flow` is not assigned if `rte_flow_validate()` returns non-0= .

--
Regards,
Vladimir

--000000000000dee4a5062d52f79f--