[dpdk-dev] [PATCH v3] app/testpmd: print Rx/Tx offload values

Van Haaren, Harry harry.van.haaren at intel.com
Tue Mar 13 10:24:58 CET 2018


> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Monday, March 12, 2018 5:53 PM
> To: Lu, Wenzhuo <wenzhuo.lu at intel.com>; Wu, Jingjing <jingjing.wu at intel.com>
> Cc: dev at dpdk.org; Yigit, Ferruh <ferruh.yigit at intel.com>; Shahaf Shuler
> <shahafs at mellanox.com>; Yongseok Koh <yskoh at mellanox.com>
> 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 since Rx/Tx offload values covers it and printing only CRC one
> can cause confusion.
> 
> Hexadecimal offloads values are not very user friendly but preferred to
> not create to much noise during forwarding start.


Hmmm - I'm thinking is there a better method to reduce verbosity, but keep
user friendliness?

Can the dynamic logs be used? By default, just print the hex mask, but with
--log-level="pmd.net.*.offload_flags" we print the list, itemized?

crc strip .......... 1
vlan strip ......... 1
udp checksum ....... 0


I'm not sure what the exact string should be - testpmd specific or DPDK wide at the PMD level?


More information about the dev mailing list