DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tapio Tallgren <tapio.tallgren@gmail.com>
To: Shankari Vaidyalingam <shankari.v2k6@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Query on the modified rte_mbuf structure
Date: Tue, 30 Dec 2014 08:58:01 +0200	[thread overview]
Message-ID: <CAJi57Q=d4yaL9xFf2TWLgFapjmVJzUak8nkPf5X2WXsn6cgULw@mail.gmail.com> (raw)
In-Reply-To: <CAGeyXNd0gvMrB-pst=JvCeJdN4ut78X6Lf4nvZw+BEon7hRHSQ@mail.gmail.com>

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@gmail.com> 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

  reply	other threads:[~2014-12-30  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-25  9:24 Shankari Vaidyalingam
2014-12-30  6:58 ` Tapio Tallgren [this message]
2015-01-05 12:03   ` Bruce Richardson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJi57Q=d4yaL9xFf2TWLgFapjmVJzUak8nkPf5X2WXsn6cgULw@mail.gmail.com' \
    --to=tapio.tallgren@gmail.com \
    --cc=dev@dpdk.org \
    --cc=shankari.v2k6@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).