* Query on the modified rte_mbuf structure @ 2014-12-25 9:24 Shankari Vaidyalingam [not found] ` <CAGeyXNd0gvMrB-pst=JvCeJdN4ut78X6Lf4nvZw+BEon7hRHSQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 3+ messages in thread From: Shankari Vaidyalingam @ 2014-12-25 9:24 UTC (permalink / raw) To: dev-VfR2kkLFssw Hi, I can see that in the recent releases of DPDK the rte_mbuf structure has undergone some changes. Would like to know which field in the rte_mbuf data structure holds the exact payload of the received packet in the modified structure. Regards Shankari ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <CAGeyXNd0gvMrB-pst=JvCeJdN4ut78X6Lf4nvZw+BEon7hRHSQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Query on the modified rte_mbuf structure [not found] ` <CAGeyXNd0gvMrB-pst=JvCeJdN4ut78X6Lf4nvZw+BEon7hRHSQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2014-12-30 6:58 ` Tapio Tallgren [not found] ` <CAJi57Q=d4yaL9xFf2TWLgFapjmVJzUak8nkPf5X2WXsn6cgULw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 3+ messages in thread From: Tapio Tallgren @ 2014-12-30 6:58 UTC (permalink / raw) To: Shankari Vaidyalingam; +Cc: dev-VfR2kkLFssw Hi, I am not sure if I understand the question correctly, but there was a change to the rte_mbuf structure with patch ea672a8b1655bbb44876d2550ff56f384968a43b. It got rid of the pkt member in rte_mbuf. Here is an example of how to fix it: - eth_hdr = (struct ether_hdr *) mb->pkt.data; + eth_hdr = (struct ether_hdr *) mb->data; Another way of answering your question is that it is "data" in rte_mbuf: - struct rte_pktmbuf pkt; + /* valid for any segment */ + struct rte_mbuf *next; /**< Next segment of scattered packet. */ + void* data; /**< Start address of data in segment buffer. */ + uint16_t data_len; /**< Amount of data in segment buffer. */ On Thu, Dec 25, 2014 at 11:24 AM, Shankari Vaidyalingam < shankari.v2k6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > Hi, > > > I can see that in the recent releases of DPDK the rte_mbuf structure has > undergone some changes. > Would like to know which field in the rte_mbuf data structure holds the > exact payload of the received packet in the modified structure. > > Regards > Shankari > -- -Tapio ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <CAJi57Q=d4yaL9xFf2TWLgFapjmVJzUak8nkPf5X2WXsn6cgULw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Query on the modified rte_mbuf structure [not found] ` <CAJi57Q=d4yaL9xFf2TWLgFapjmVJzUak8nkPf5X2WXsn6cgULw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2015-01-05 12:03 ` Bruce Richardson 0 siblings, 0 replies; 3+ messages in thread From: Bruce Richardson @ 2015-01-05 12:03 UTC (permalink / raw) To: Tapio Tallgren; +Cc: dev-VfR2kkLFssw On Tue, Dec 30, 2014 at 08:58:01AM +0200, Tapio Tallgren wrote: > Hi, > > I am not sure if I understand the question correctly, but there was a > change to the rte_mbuf structure with > patch ea672a8b1655bbb44876d2550ff56f384968a43b. It got rid of the pkt > member in rte_mbuf. Here is an example of how to fix it: > > - eth_hdr = (struct ether_hdr *) mb->pkt.data; > + eth_hdr = (struct ether_hdr *) mb->data; > > Another way of answering your question is that it is "data" in rte_mbuf: > > - struct rte_pktmbuf pkt; > + /* valid for any segment */ > + struct rte_mbuf *next; /**< Next segment of scattered packet. */ > + void* data; /**< Start address of data in segment > buffer. */ > + uint16_t data_len; /**< Amount of data in segment buffer. */ > > > > > On Thu, Dec 25, 2014 at 11:24 AM, Shankari Vaidyalingam < > shankari.v2k6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > Hi, > > > > > > I can see that in the recent releases of DPDK the rte_mbuf structure has > > undergone some changes. > > Would like to know which field in the rte_mbuf data structure holds the > > exact payload of the received packet in the modified structure. > > > > Regards > > Shankari > > > > Best way to get at the packet data is to use the rte_pktmbuf_mtod macro defined in rte_mbuf.h. This macro should be always kept up-to-date to refer to the packet data, irrespective of changes to the underlying data structure. /Bruce ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-01-05 12:03 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2014-12-25 9:24 Query on the modified rte_mbuf structure Shankari Vaidyalingam [not found] ` <CAGeyXNd0gvMrB-pst=JvCeJdN4ut78X6Lf4nvZw+BEon7hRHSQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2014-12-30 6:58 ` Tapio Tallgren [not found] ` <CAJi57Q=d4yaL9xFf2TWLgFapjmVJzUak8nkPf5X2WXsn6cgULw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2015-01-05 12:03 ` Bruce Richardson
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.