From: Meir Tseitlin <mirots@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_pktmbuf_alloc fails
Date: Tue, 1 Apr 2014 14:53:47 +0300 [thread overview]
Message-ID: <CA+Typ9kU8bPfT-9Be9O6uRAK-YWyJYAiMbtoCtbvXy4jQM-nJA@mail.gmail.com> (raw)
In-Reply-To: <CA+Typ9mJRUhSbOME=r3KFADxykKYN8snVAZ1JUEf8ohXbz-W7w@mail.gmail.com>
I think I found the problem - it was solved by manually calling
rte_pktmbuf_free for each packet.
It seems that rte_pktmbuf_free is not automatically called from
within rte_eth_tx_burst if packets are sent to pcap device.
Is it possible?
On Tue, Apr 1, 2014 at 2:08 PM, Meir Tseitlin <mirots@gmail.com> wrote:
> Hi,
>
> I modified l2fwd example to "inject" additional Ethernet packets into the
> flow by allocating them with rte_pktmbuf_alloc.
>
> I do succeed to call rte_pktmbuf_alloc when none (or almost none) packets
> where forwarded since application start, but it fails when application is
> busy handling traffic (even light traffic).
>
> Following Intel developers guide suggestion about thread safety, I am
> calling this function within the same CPU core I am about to send the
> packet.
>
> Any ideas?
>
> Thanks
> Meir Tseitlin
>
--
Kind regards,
*Meir Tseitlin*
Software architect*Mobile:* +972.54.7647417
*Fax:* +972.72.2812365
*Email:* meir.tech@gmail.com
*http://il.linkedin.com/in/meirts <http://il.linkedin.com/in/meirts>*
*Independent consultant*
<http://maps.google.com/maps?q=&hl=en>
See who we know in
common<http://www.linkedin.com/e/wwk/6408776/?hs=false&tok=2g4qg82N8Sb5U1>Want
a signature like
this?<http://www.linkedin.com/e/sig/6408776/?hs=false&tok=20mz9jA_USb5U1>
next prev parent reply other threads:[~2014-04-01 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 11:08 Meir Tseitlin
2014-04-01 11:53 ` Meir Tseitlin [this message]
2014-04-07 7:26 ` Olivier MATZ
2014-04-07 8:53 ` Ananyev, Konstantin
2014-04-17 15:00 ` Thomas Monjalon
2014-05-22 15:47 ` Thomas Monjalon
2014-05-22 15:51 ` 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=CA+Typ9kU8bPfT-9Be9O6uRAK-YWyJYAiMbtoCtbvXy4jQM-nJA@mail.gmail.com \
--to=mirots@gmail.com \
--cc=dev@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).