DPDK usage discussions
 help / color / mirror / Atom feed
From: Cliff Burdick <shaklee3@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] Wrong Data In Buffer After Upgrade To 17.02.1
Date: Wed, 21 Jun 2017 08:42:19 -0700	[thread overview]
Message-ID: <CA+Gp1nbqUiXE5z8ygMua=EMH2W7XM0mavbyQaZqumDQYwMwFGw@mail.gmail.com> (raw)

Hi, I upgraded from 2.2.0 to 17.02.1 using the i40e driver, and I'm seeing
very weird behavior that's easily reproducible. My receiving thread/lcore
calls rte_eth_rx_burst(), changes the endianess on some of the packet
headers, and puts the pktmbuf onto a ring for the next eal thread to
process and eventually free. After upgrading, I'm seeing that
when rte_eth_rx_burst starts reusing buffers from the mempool, it's
returning buffers that don't have the new packet's data, but rather the old
data where I had already changed the endianess on some of the headers. I
removed the ring part, and even doing:

1) rte_eth_rx_burst
2) Change endianness
3) free pktmbuf

all within the same thread causes this issue to happen too. I've looked
through the changelog and don't see anything obvious that would be causing
this. Has anyone seen this happen? Thanks

             reply	other threads:[~2017-06-21 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 15:42 Cliff Burdick [this message]
2017-06-30 20:38 ` Cliff Burdick

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='CA+Gp1nbqUiXE5z8ygMua=EMH2W7XM0mavbyQaZqumDQYwMwFGw@mail.gmail.com' \
    --to=shaklee3@gmail.com \
    --cc=users@dpdk.org \
    /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).