gt; >> From: Ferruh Yigit
> >> Sent: Friday, November 6, 2020 7:20 PM
> >> To: Bing Zhao ; Slava Ovsiienko
> >> ; Matan Azrad
> >> Cc: dev@dpdk.org; Ori Kam ; Raslan Darawsheh
> >> ; sta...@dpdk.org
> >> Subject: Re: [dpdk-dev] [PATCH] net/m
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix the eCPRI common
header endianness
External email: Use caution opening links or attachments
On 11/3/2020 5:41 AM, Bing Zhao wrote:
The input header of a RTE flow item is with network byte order. In
the
host with little endian, the bit field order are
t: Re: [dpdk-dev] [PATCH] net/mlx5: fix the eCPRI common
> header endianness
>
> External email: Use caution opening links or attachments
>
>
> On 11/3/2020 5:41 AM, Bing Zhao wrote:
> > The input header of a RTE flow item is with network byte order. In
> the
> >
On 11/3/2020 5:41 AM, Bing Zhao wrote:
The input header of a RTE flow item is with network byte order. In
the host with little endian, the bit field order are the same as the
byte order.
When checking the an eCPRI message type, the wrong field will be
selected. Right now, since the whole u32 is b
Hi,
> -Original Message-
> From: Bing Zhao
> Sent: Tuesday, November 3, 2020 7:42 AM
> To: Slava Ovsiienko ; Matan Azrad
>
> Cc: dev@dpdk.org; Ori Kam ; Raslan Darawsheh
> ; sta...@dpdk.org
> Subject: [PATCH] net/mlx5: fix the eCPRI common header endianness
>
> The input header of a RTE
The input header of a RTE flow item is with network byte order. In
the host with little endian, the bit field order are the same as the
byte order.
When checking the an eCPRI message type, the wrong field will be
selected. Right now, since the whole u32 is being checked and for
all types, the follo
6 matches
Mail list logo
