Sabu,
I think that in this case the packet length is zero which will result in
nothing from mtod.
Daniel
On Sun, Mar 16, 2014 at 3:03 PM, sabu kurian wrote:
> Hello chris,
>
> Thanks for your reply. I tried dumping the contents of mbuf as you have
> suggested.
> This is what I get:
>
> dump m
Hello chris,
Thanks for your reply. I tried dumping the contents of mbuf as you have
suggested.
This is what I get:
dump mbuf at 0x0x6c7620, phys=7f34d91eba28, buf_len=59488
pkt_len=0, ol_flags=0, nb_segs=0, in_port=0
and soon after that I get a segmentation fault. Do you have any idea on
what c
Hello friends,
I'm trying to print the ether_type for a packet that I captured from a port
on my machine. Suppose 'm' holds the packet. 'm' is of type 'struct
rte_mbuf'. Intels API reference for DPDK says 'ether_type' is of uint16_t.
I used the following code to retrieve ether_type.
void * eth_ty
* sabu kurian (sabu2kurian at gmail.com) wrote:
> Hello friends,
>
> I'm trying to print the ether_type for a packet that I captured from a port
> on my machine. Suppose 'm' holds the packet. 'm' is of type 'struct
> rte_mbuf'. Intels API reference for DPDK says 'ether_type' is of uint16_t.
> I us
4 matches
Mail list logo