From: "Neeraj Tandon (netandon)" <netandon@cisco.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] MBUF messed up between EAL and NON EAL threads
Date: Wed, 31 May 2017 03:28:50 +0000 [thread overview]
Message-ID: <E8946232-66B2-406A-BBDB-842842D768F1@cisco.com> (raw)
Hi,
I am seeing an MBUF issue between two threads communicating using a Ring of MBUFs. I would appreciate if someone can tell if this is correct method to accomplish this:
1. Master Core creates MBUF pool and a ring.
2. An EAL Transmit thread polls this Ring
3. A NON EAL threads allocates a MBUF from this pool and queues in the ring
4. EAL Transmit thread deques and transmits the MBUF
Here is the issue I am seeing:
In NON EAL Thread where MBUF is allocated, the mbuf dump shows :
dump mbuf at 0x7f3b9339aa80, phys=11339ab00, buf_len=2176
pkt_len=34, ol_flags=f0000000000000, nb_segs=1, in_port=1
segment at 0x7f3b9339aa80, data=0x7f3b9339ab80, data_len=34
In Transmit thread on dequeuing;
dump mbuf at 0x7f3b9339ab00, phys=0, buf_len=0
pkt_len=0, ol_flags=0, nb_segs=0, in_port=0
So mbuf address is messed up and none of the other values are good. Any idea, suggestion most welcome. Should I be only using EAL thread to send to Ring but that is highly limiting in design
Regards,
Neeraj
next reply other threads:[~2017-05-31 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 3:28 Neeraj Tandon (netandon) [this message]
2017-06-01 10:18 ` Padam Jeet Singh
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=E8946232-66B2-406A-BBDB-842842D768F1@cisco.com \
--to=netandon@cisco.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).