From: Sushil Adhikari <sushil446@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Crafting dpdk packet in secondary application and sending them from primary application, multi-process, dpdk
Date: Wed, 29 Mar 2017 16:01:24 -0500 [thread overview]
Message-ID: <CAPO9LfRAmUTQMZq39sGCnD17LnFTp_cM4V4em6P_4t44+pza3g@mail.gmail.com> (raw)
I have two dpdk application one primary with "--proc-type=primary" which
does kni packet forwarding(as in kni example application) and a secondary
application with "--proc-type=secondary" whose job is to craft dpdk packets
from raw data and forward them through the memory(buffer) set up in primary
application. I'm having problem allocating mbuf for packet crafting in
secondary application.
To get mbuf what I did was (in secondary application)
struct rte_mbuf *buffer =
rte_pktmbuf_alloc(rte_mempool_lookup("mempool_name"));
but this doesnt give me rte_mbuf rather it hangs the program, this probably
is because I can't allocate memory (rte_mbuf*) in secondary application
from mempool created by primary application.
How can I craft packet on secondary application and how can I send them
through the kni interface created in primary application.
I would appreciate any help or suggestions.
Thank you
Sushil
reply other threads:[~2017-03-29 21:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAPO9LfRAmUTQMZq39sGCnD17LnFTp_cM4V4em6P_4t44+pza3g@mail.gmail.com \
--to=sushil446@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).