From: "Mario Gianni" <m.gianni-Gbsd49wXnelWk0Htik3J/w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: problem with rte_pktmbuf_prepend (possible bug?)
Date: Tue, 18 Feb 2014 05:27:49 -0500 [thread overview]
Message-ID: <20140218102749.270040@gmx.com> (raw)
Hi all, I'm experimenting some code with DPDK v1.5.0 and I have the following problem:
I have a thread that receives packets from NIC, once I received a packet I want to prepend some data to it and I try to do so through the function rte_pktmbuf_prepend()
then the packet is enqueued in a ring buffer where it will be used by a client thread before being dropped through the function rte_pktmbuf_free() called by the client thread.
Now, if I try to send packets to this program I have the following behaviour:
In a first time it seems to work correctly, then after a certain number of received packets (approximately the same number as the number of mbufs present in the mempool) if I call the rte_pktmbuf_headroom it returns that the headroom is shrinking more than the expected, until after a certain number of packets the headroom goes to zero.
It seems like that when I call the rte_pktmbuf_free() function it doesn't reset the data position inside the mbuf, so when I call for a second time the mbuf the headroom continues to shrink until it finishes.
Do you have any idea of this strange behaviour?Could it be a bug in the prepend/free function?
Thank you,
Mario
next reply other threads:[~2014-02-18 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 10:27 Mario Gianni [this message]
[not found] ` <20140218102749.270040-KK0ffGbhmjU@public.gmane.org>
2014-02-18 14:19 ` problem with rte_pktmbuf_prepend (possible bug?) Periklis Akritidis
[not found] ` <78841534-98AB-4845-9FAF-CAC975D15D3A-wlH+TjtWvpzuufBYgWm87A@public.gmane.org>
2014-02-18 17:16 ` Benson, Bryan
-- strict thread matches above, loose matches on Subject: below --
2014-02-19 14:04 Mario Gianni
[not found] ` <20140219140433.259460-KK0ffGbhmjU@public.gmane.org>
2014-02-19 17:32 ` Ananyev, Konstantin
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=20140218102749.270040@gmx.com \
--to=m.gianni-gbsd49wxnelwk0htik3j/w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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).