DPDK usage discussions
 help / color / mirror / Atom feed
From: Alex Kiselev <alex@therouter.net>
To: users@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-users] sending a mbuf clone to KNI
Date: Mon, 30 Jul 2018 11:59:46 +0300	[thread overview]
Message-ID: <331592539.20180730115946@therouter.net> (raw)

Hi.

Is it safe to send a mbuf clone to a KNI interface?
I had a lot of troubles while doing so. At first my KNI
interfaces stoped working after a while while my application 
was still forwarding packets. Then my app started almost
immediately crash. Then I changed a code a little bit
and rather sending a mbuf clone to KNI I switched to sending
a mbuf to KNI and send a mbuf clone to the second destination (another lcore).
So far, this approach works good.

So, I would say that it's not safe.
But why?

And is it safe to send a mbuf to KNI and its clone to another core at the same time?

Thanks. 

                 reply	other threads:[~2018-07-30  9:00 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=331592539.20180730115946@therouter.net \
    --to=alex@therouter.net \
    --cc=ferruh.yigit@intel.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).