-14.2.0
arc axs101_defconfiggcc-14.1.0
arc defconfiggcc-14.2.0
arc randconfig-001-20250326gcc-14.2.0
arc randconfig-002-20250326gcc-8.5.0
arm allmodconfigclang-19
allnoconfiggcc-14.2.0
arc allyesconfiggcc-14.2.0
arc randconfig-001-20250326gcc-14.2.0
arc randconfig-002-20250326gcc-8.5.0
arm allmodconfiggcc-14.2.0
arm
-14.2.0
arc allyesconfiggcc-14.2.0
arc randconfig-001-20250326gcc-14.2.0
arc randconfig-002-20250326gcc-8.5.0
arm allmodconfiggcc-14.2.0
arm allnoconfigclang
On 2025-03-26 11:14 a.m., Alexander Lobakin wrote:
From: Ahmed Zaki
Date: Mon, 24 Mar 2025 07:49:36 -0600
Add basic flow steering. For now, we support IPv4 and TCP/UDP only.
1. Very poor cover letter. I'd suggest describing a bit more here.
I'd call it concise. Let me know what is miss
From: Ahmed Zaki
Date: Mon, 24 Mar 2025 07:49:38 -0600
> Use the new virtchnl2 OP codes to communicate with the Control Plane to
> add flow steering filters. We add the basic functionality for ADD/Delete
> with TCP/UDP IPv4 only. Support for other OP codes and protocols will be
> added later.
>
From: Ahmed Zaki
Date: Mon, 24 Mar 2025 07:49:36 -0600
> Add basic flow steering. For now, we support IPv4 and TCP/UDP only.
1. Very poor cover letter. I'd suggest describing a bit more here.
2. net-next is closed, so this is RFC at max.
3. I haven't seen this reviewed properly on our internal M
figgcc-14.2.0
arc allmodconfiggcc-14.2.0
arc allnoconfiggcc-14.2.0
arc allyesconfiggcc-14.2.0
archsdk_defconfiggcc-14.2.0
arc randconfig-001-20250
