From: Pavel Vajarov <freakpv@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] Handling KNI in a secondary process
Date: Wed, 1 Jul 2020 12:48:52 +0300 [thread overview]
Message-ID: <CAK9EM1_4ykyGz74dDGtuEmkK0JOWXBNPhPO9rGjCoY0UUOdLBA@mail.gmail.com> (raw)
Hi there,
Basically my question is whether it's possible to handle KNI packets
(rte_kni_tx_burst, rte_kni_handle_request, rte_kni_rx_burst) in a secondary
process?
My idea to do this is to avoid slowing down the primary process with KNI
handling. I'm thinking of using a shared memory ring buffer to send the
needed packets to the secondary process (just like in the
mulitprocess/client_server_mp example) and then the secondary process will
do the KNI processing. Is this setup possible?
I'm asking this because I read that the rte_kni_init function that
"This function is to be executed on the MASTER lcore only" and I was
wondering will I be able to use the kni related functions from a secondary
process?
Or maybe I need to initialize the KNI in the master process and then
use rte_kni_get before start using the KNI?
Thanks,
Pavel.
next reply other threads:[~2020-07-01 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 9:48 Pavel Vajarov [this message]
2020-07-01 13:00 ` Cliff Burdick
2020-07-01 13:09 ` Pavel Vajarov
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=CAK9EM1_4ykyGz74dDGtuEmkK0JOWXBNPhPO9rGjCoY0UUOdLBA@mail.gmail.com \
--to=freakpv@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).