From: Alex Markuze <alex@weka.io>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] nic loopback
Date: Mon, 20 Oct 2014 19:24:08 +0300 [thread overview]
Message-ID: <CAKfHP0VYMjcHuMhS814j+R_TQjWFeJ3Zkffm4oaQ7+ZZXTdsJQ@mail.gmail.com> (raw)
Hi,
I'm trying to send packets from an application to it self, meaning smac ==
dmac.
I'm working with intel 82599 virtual function. But it seems that these
packets are lost.
Is there a software/hw limitation I'm missing here (some additional
anti-spoofing)? AFAIK modern NICs with sriov are mini switches so the hw
loopback should work, at least thats the theory.
Thanks.
next reply other threads:[~2014-10-20 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 16:24 Alex Markuze [this message]
2014-10-21 1:18 ` Liang, Cunming
2014-10-21 15:16 ` Alex Markuze
2014-10-22 3:33 ` Liang, Cunming
2014-10-22 4:37 ` [dpdk-dev] FW: " Zhu, Heqing
2014-10-22 7:42 ` alex
2014-10-22 8:04 ` Liang, Cunming
2014-10-21 15:32 ` [dpdk-dev] " Thomas Monjalon
2014-10-21 15:54 ` Alex Markuze
2014-10-21 20:14 ` Thomas Monjalon
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=CAKfHP0VYMjcHuMhS814j+R_TQjWFeJ3Zkffm4oaQ7+ZZXTdsJQ@mail.gmail.com \
--to=alex@weka.io \
--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).