From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <tapiotallgren@gmail.com> Received: from mail-ig0-f172.google.com (mail-ig0-f172.google.com [209.85.213.172]) by dpdk.org (Postfix) with ESMTP id 4DADF5A03 for <dev@dpdk.org>; Tue, 30 Dec 2014 07:58:22 +0100 (CET) Received: by mail-ig0-f172.google.com with SMTP id a13so1444232igq.17 for <dev@dpdk.org>; Mon, 29 Dec 2014 22:58:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=C8SD3QU+a81a5Ar6A4cEBfW4uf+cBl736sXp3EWUvsY=; b=Z/aBbIwFypLVxpJaJwbZptO2kqRB9BUBkf3ThHUEVrjOLdrhsDDlyd02vuenRtXTU/ hNZKa0PG7YE4tCyeJlcB/YtFnKuxcY6y8SjIesw38kSPdEdcyrNvGIU7xTmspEIVxc/6 S7Ws74Ug4O3YfhY4008Dg84mLxucl+PgVoML3P4zxYLleEBAlqFdzlIIXg0Q2Wpmx92T SD8x/gGqA4R0h1U20XMGAVJAk2h8yaWw2O4E+zCMGLDMRjHaItzZylaGTgkBrBrD1jLn igTLk1PfJFFWbvA7yireRw/t2/otZsuWtqOqaS3v8opteGKzLkRnRfQvGlbdLSIDI9WX W99w== X-Received: by 10.50.30.3 with SMTP id o3mr3791087igh.44.1419922701520; Mon, 29 Dec 2014 22:58:21 -0800 (PST) MIME-Version: 1.0 Sender: tapiotallgren@gmail.com Received: by 10.50.62.15 with HTTP; Mon, 29 Dec 2014 22:58:01 -0800 (PST) In-Reply-To: <CAGeyXNd0gvMrB-pst=JvCeJdN4ut78X6Lf4nvZw+BEon7hRHSQ@mail.gmail.com> References: <CAGeyXNd0gvMrB-pst=JvCeJdN4ut78X6Lf4nvZw+BEon7hRHSQ@mail.gmail.com> From: Tapio Tallgren <tapio.tallgren@gmail.com> Date: Tue, 30 Dec 2014 08:58:01 +0200 X-Google-Sender-Auth: ht5z73gHBwM5guiyjNUkOf86Neg Message-ID: <CAJi57Q=d4yaL9xFf2TWLgFapjmVJzUak8nkPf5X2WXsn6cgULw@mail.gmail.com> To: Shankari Vaidyalingam <shankari.v2k6@gmail.com> Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Query on the modified rte_mbuf structure X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 30 Dec 2014 06:58:22 -0000 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