ara
> <ciara.lof...@intel.com>;
> santosh.shu...@caviumnetworks.com
> Subject: RE: [ovs-dev][RFC PATCH V4 5/9] dp-packet: init specific mbuf fields
> to
> 0
>
> >From: Chandran, Sugesh
> >Sent: Friday, December 8, 2017 6:00 PM
> >To: Kavanagh, Mark B <ma
switch.org; qiud...@chinac.com
>> Cc: Stokes, Ian <ian.sto...@intel.com>; Loftus, Ciara
><ciara.lof...@intel.com>;
>> santosh.shu...@caviumnetworks.com; Chandran, Sugesh
>> <sugesh.chand...@intel.com>; Kavanagh, Mark B
>> <mark.b.kavan...@intel.com>
&g
u...@caviumnetworks.com; Chandran, Sugesh
> <sugesh.chand...@intel.com>; Kavanagh, Mark B
> <mark.b.kavan...@intel.com>
> Subject: [ovs-dev][RFC PATCH V4 5/9] dp-packet: init specific mbuf fields to 0
>
> dp_packets are created using xmalloc(); in the case of OvS-DPDK, it'
dp_packets are created using xmalloc(); in the case of OvS-DPDK, it's
possible the the resultant mbuf portion of the dp_packet contains
random data. For some mbuf fields, specifically those related to
multi-segment mbufs and/or offload features, random values may cause
unexpected behaviour, should
