From: "Rosen, Rami" <rami.rosen@intel.com>
To: Alex Kiselev <kiselev99@gmail.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] assert failure while allocating cmbuf
Date: Mon, 15 Jan 2018 23:12:11 +0000 [thread overview]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F94C3AE725@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <CAMKNYby622gh3zihj+6Jv0eQiVRwA=oYGSHFpYz9ahpTDWM+HA@mail.gmail.com>
Alex,
Are you aware of the ongoing deprecation process of ctrl_mbuf API ?
See for example, this thread:
http://dev.dpdk.narkive.com/EifFAcs5/dpdk-dev-rte-ctrlmbuf-init-and-ctrl-mbuf-flag-are-not-used-shouldn-t-they-be-removed-and-deprecated
Regards,
Rami Rosen
-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of Alex Kiselev
Sent: Sunday, January 14, 2018 14:37
To: users <users@dpdk.org>
Subject: [dpdk-users] assert failure while allocating cmbuf
Hi.
I've got an error in my application and I need an advice how to find what could cause it.
The error was RTE_ASSERT(rte_mbuf_refcnt_read(m) == 0) failure in
rte_mbuf_raw_alloc()
while my app was trying to allocate a new mbuf from a control memory buffer pool using rte_ctrlmbuf_alloc(). So, that kinda mbufs are used only for passing messages via rings in my app.
What should I look for in order to find a bug in my app?
Thank you.
P.S.
So far I've got only one occurrence of the bug and I am trying to reproduce it running the same stress test.
--
Alex Kiselev
prev parent reply other threads:[~2018-01-15 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 12:37 Alex Kiselev
2018-01-15 23:12 ` Rosen, Rami [this message]
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=9B0331B6EBBD0E4684FBFAEDA55776F94C3AE725@HASMSX110.ger.corp.intel.com \
--to=rami.rosen@intel.com \
--cc=kiselev99@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).