On Thu, Aug 24, 2023 at 2:04 PM Ilya Maximets wrote:
>
> On 8/22/23 10:11, David Marchand wrote:
> > OVS current sets RTE_MBUF_F_TX_IPV[46] flags in early stages of the
> > packet reception and keeps track of the IP packet type as the packet
> > goes through OVS pipeline.
> > When a packet leaves
On 8/22/23 10:11, David Marchand wrote:
> OVS current sets RTE_MBUF_F_TX_IPV[46] flags in early stages of the
> packet reception and keeps track of the IP packet type as the packet
> goes through OVS pipeline.
> When a packet leaves OVS and hits a DPDK driver, OVS may not request IP
> checksum
On Tue, Aug 22, 2023 at 4:11 AM David Marchand
wrote:
>
> OVS current sets RTE_MBUF_F_TX_IPV[46] flags in early stages of the
> packet reception and keeps track of the IP packet type as the packet
> goes through OVS pipeline.
> When a packet leaves OVS and hits a DPDK driver, OVS may not request
Bleep bloop. Greetings David Marchand, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line lacks whitespace around operator
#31 FILE: lib/netdev-dpdk.c:2434:
OVS current sets RTE_MBUF_F_TX_IPV[46] flags in early stages of the
packet reception and keeps track of the IP packet type as the packet
goes through OVS pipeline.
When a packet leaves OVS and hits a DPDK driver, OVS may not request IP
checksum offloading but leaves one of this packet type flag in
