[dpdk-users] Why packet_type is zero?
thomas.monjalon at 6wind.com
Tue Nov 10 15:55:06 CET 2015
Thanks for reporting.
2015-11-10 15:46, Arseniy Zaostrovnykh:
> Is the pcap driver obsolete?
> L3fwd example(http://dpdk.org/doc/guides/sample_app_ug/l3_forward.html)
> check the mbuf field packet_type, and in the zero case (which is a
> default value, as far as I know) it does nothing. At the same time, only
> few drivers even mention this field:
> dpdk-2.1.0 $ grep packet_type drivers -Rl
> And a PCap driver (drivers/net/pcap/rte_eth_pcap.c) specifically, does
> not alter the field, so L3fwd application drops all packets.
The zero value is acceptable.
#define RTE_PTYPE_UNKNOWN 0x00000000
Maybe a fix is required in the l3fwd example?
Or maybe it should be explicit that it works with only few drivers.
More generally, the packet type is not mandatory for drivers.
At a time we were talking about implementing a generic callback to
fill it. Or it can be filled in an application fallback with parsing.
More information about the users