From: Antonio Di Bacco <a.dibacco.ks@gmail.com>
To: users@dpdk.org
Subject: Connecting two DPDK applications through fake virtual functions
Date: Thu, 17 Mar 2022 10:29:25 +0100 [thread overview]
Message-ID: <CAO8pfF=7CCmyZVPC1omVyxvF7uujN+S59UyxbBS=5dNPhbu2oQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
I have two DPDK applications that are using virtual functions built on top
of two physical functions that correspond to the two ports of a 25 Gbps
ethernet card. The two physical ports are connected one to the other with
an optic fiber.
Now, I would like to realize the same setup but without using a physical 25
Gbps card, I wonder if this is possible.
[-- Attachment #2: Type: text/html, Size: 407 bytes --]
next reply other threads:[~2022-03-17 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 9:29 Antonio Di Bacco [this message]
2022-03-17 13:26 ` Timothy Wood
2022-03-17 15:55 ` Antonio Di Bacco
2022-03-17 16:44 ` Dmitry Kozlyuk
2022-03-17 20:53 ` Antonio Di Bacco
2022-03-17 21:41 ` Dmitry Kozlyuk
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='CAO8pfF=7CCmyZVPC1omVyxvF7uujN+S59UyxbBS=5dNPhbu2oQ@mail.gmail.com' \
--to=a.dibacco.ks@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).