12/03/2018 18:53, Ferruh Yigit:
> Which per port offloads are enabled is not clear. Printing offloads
> values at forwarding start.
>
> CRC strip offload value was printed in more verbose manner, it is
> removed since Rx/Tx offload values covers it and printing only CRC one
> can cause confusion.
> -Original Message-
> From: Yigit, Ferruh
> Sent: Tuesday, March 13, 2018 10:21 AM
> To: Van Haaren, Harry ; Lu, Wenzhuo
> ; Wu, Jingjing
> Cc: dev@dpdk.org; Shahaf Shuler ; Yongseok Koh
>
> Subject: Re: [dpdk-dev] [PATCH v3] app/testpmd: print Rx/Tx offload va
; Subject: [dpdk-dev] [PATCH v3] app/testpmd: print Rx/Tx offload values
>>
>> Which per port offloads are enabled is not clear. Printing offloads
>> values at forwarding start.
>>
>> CRC strip offload value was printed in more verbose manner, it is
>> removed sin
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Monday, March 12, 2018 5:53 PM
> To: Lu, Wenzhuo ; Wu, Jingjing
> Cc: dev@dpdk.org; Yigit, Ferruh ; Shahaf Shuler
> ; Yongseok Koh
> Subject: [dpdk-dev] [PATCH v3] app/testpmd: print Rx/Tx offload val
Which per port offloads are enabled is not clear. Printing offloads
values at forwarding start.
CRC strip offload value was printed in more verbose manner, it is
removed since Rx/Tx offload values covers it and printing only CRC one
can cause confusion.
Hexadecimal offloads values are not very us
5 matches
Mail list logo