Hi,
> -Original Message-
> From: Michael Baum
> Sent: Thursday, January 25, 2024 2:37 PM
> To: dev@dpdk.org
> Cc: Matan Azrad ; Dariusz Sosnowski
> ; Raslan Darawsheh ; Slava
> Ovsiienko ; Ori Kam ;
> Suanming Mou
> Subject: [PATCH v5 0/2] net/mlx5: add random item support
>
> Add suppo
> From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
> Sent: Saturday, 27 January 2024 20.15
>
> On 2024-01-26 11:18, Morten Brørup wrote:
> >> From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
> >> Sent: Friday, 26 January 2024 11.05
> >>
> >> On 2024-01-25 23:53, Morten Brørup wrote:
> >>
This patch set adds the support for encap hash calculation.
It is based on RFC:
https://patchwork.dpdk.org/project/dpdk/patch/20231210083100.7893-1-or...@nvidia.com/
Hamdan Igbaria (1):
net/mlx5/hws: introduce encap entropy hash calculation API
Ori Kam (3):
ethdev: introduce encap hash calcu
During the encapsulation of a packet, it is expected to calculate the
hash value which is based on the original packet (the outer values,
which will become the inner values).
The tunnel protocol defines which tunnel field should hold this hash,
but it doesn't define the hash calculation algorithm.
From: Hamdan Igbaria
Add new function for encap entropy hash calculation, the function
will check the device capability for the entropy hash type used
by the device, and will calculate the entropy hash value of the
user passed fields according this type.
Signed-off-by: Hamdan Igbaria
---
drive
This commit adds support for encap hash calculation.
Signed-off-by: Ori Kam
---
drivers/net/mlx5/mlx5_flow.c| 29 +++
drivers/net/mlx5/mlx5_flow.h| 8
drivers/net/mlx5/mlx5_flow_hw.c | 66 +
3 files changed, 103 insertions(+)
diff --git
This commits add support for calculating the encap hash.
Command structure:
flow hash {port} encap {target field} pattern {item} [/ {item} [...] ] / end
Example:
calculate hash to be used by VXLAN encapsulation.
flow hash 0 encap hash_field_sport pattern ipv4 dst is 7.7.7.7 src is 8.8.8.8
/ ud
On 2024-01-28 09:57, Morten Brørup wrote:
From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
Sent: Saturday, 27 January 2024 20.15
On 2024-01-26 11:18, Morten Brørup wrote:
From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
Sent: Friday, 26 January 2024 11.05
On 2024-01-25 23:53, Morten
Add support for compare item with "RTE_FLOW_FIELD_RANDOM".
Depends-on: series-30606 ("ethdev: add RTE_FLOW_ITEM_TYPE_COMPARE")
v2:
- Rebase.
- Add "RTE_FLOW_FIELD_RANDOM" compare support.
- Reduce the "Depends-on" list.
Hamdan Igbaria (1):
net/mlx5/hws: add support for compare matcher
Mich
From: Hamdan Igbaria
Add support for compare matcher, this matcher will allow
direct comparison between two packet fields, or a packet
field and a value, with fully masked DW.
For now this matcher hash table is limited to size 1x1,
thus it supports only 1 rule STE.
Signed-off-by: Hamdan Igbaria
Add support to use "RTE_FLOW_ITEM_TYPE_COMPARE" with
"RTE_FLOW_FIELD_RAMDOM" as an argument.
The random field is supported only when base is an immediate value,
random field cannot be compared with enother field.
Signed-off-by: Michael Baum
---
drivers/net/mlx5/mlx5_flow_hw.c | 70 ++
Hello,
I've uploaded the code snapshot and functional description here:
https://drive.google.com/drive/folders/1cHrPwx4fUJ6ibUCtHd4kNKsrmmvQvvOj?usp=drive_link
Regards,
Gregory
From: Jeremy Spewock
Sent: Tuesday, January 23, 2024 20:26
To: NBU-Contact-Thomas Monj
> From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
> Sent: Saturday, 27 January 2024 19.32
>
> Hi.
>
> The new timer RFC ("htimer") I submitted last year also included a new
> bitset API.
>
> https://patchwork.dpdk.org/project/dpdk/patch/20230315170342.214127-2-
> mattias.ronnb...@ericsson.
Hi Ferruh,
Kindly ping for review.
Thanks
On 2024/1/15 9:44, fengchengwen wrote:
> Kindly ping.
>
> On 2023/12/5 10:30, fengchengwen wrote:
>> Hi Ferruh,
>>
>> I notice this patchset was delegated to you, so could you take a view?
>>
>> Thanks.
>>
>> On 2023/11/6 21:11, Chengwen Feng wrote:
>>>
Hi,
On 2024/1/28 21:52, Morten Brørup wrote:
>> From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
>> Sent: Saturday, 27 January 2024 19.32
>>
>> Hi.
>>
>> The new timer RFC ("htimer") I submitted last year also included a new
>> bitset API.
>>
>> https://patchwork.dpdk.org/project/dpdk/patch/2
On (01/24/24 16:53), David Marchand wrote:
> Date: Wed, 24 Jan 2024 16:53:33 +0100
> From: David Marchand
> To: Rahul Gupta
> Cc: dev@dpdk.org, tho...@monjalon.net, bruce.richard...@intel.com,
> dmitry.kozl...@gmail.com, step...@networkplumber.org,
> sovar...@linux.microsoft.com, ok...@kernel.o
--
Please doc this command in doc/guides/testpmd_app_ug/testpmd_funcs.rst
>> Thanks, will update in next version
Also why not extend "show port rxq xxx" command to support txq ?
>> txq and rxq are different directions, so ex
On 2024-01-29 04:02, fengchengwen wrote:
Hi,
On 2024/1/28 21:52, Morten Brørup wrote:
From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
Sent: Saturday, 27 January 2024 19.32
Hi.
The new timer RFC ("htimer") I submitted last year also included a new
bitset API.
https://patchwork.dpdk.org/
On 2024-01-28 14:52, Morten Brørup wrote:
From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
Sent: Saturday, 27 January 2024 19.32
Hi.
The new timer RFC ("htimer") I submitted last year also included a new
bitset API.
https://patchwork.dpdk.org/project/dpdk/patch/20230315170342.214127-2-
ma
> From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
> Sent: Monday, 29 January 2024 07.52
>
> On 2024-01-28 14:52, Morten Brørup wrote:
> >> From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
> >> Sent: Saturday, 27 January 2024 19.32
> >>
> >> Hi.
> >>
> >> The new timer RFC ("htimer") I s
On Mon, Jan 29, 2024 at 6:35 AM Rahul Gupta
wrote:
> > Looking at what this patch does.. I am under the impression all you
> > really need is rte_eal_init without initial probing.
> > Such behavior can probably be achieved with a allowlist set to a non
> > existing device (like for example "-a 000
21 matches
Mail list logo
