DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alex Markuze <alex@weka.io>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] nic loopback
Date: Tue, 21 Oct 2014 18:54:35 +0300	[thread overview]
Message-ID: <CAKfHP0VUqUi-XThXjf89u7zGVv++P+r=OaQ5+sOaa_gCEE6ELQ@mail.gmail.com> (raw)
In-Reply-To: <1495199.x8BsTd8nYt@xps13>

Thanks Thomas,
unfortunately these patches are only valid a pf*. This is also evident from
the ixgbe pmd code which is the only one looking at this bit (lpbk_mode).
The ixgbevf functions are agnostic to this capability.

*
http://www.intel.com/content/dam/doc/design-guide/82599-sr-iov-driver-companion-guide.pdf

On Tue, Oct 21, 2014 at 6:32 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:

> 2014-10-20 19:24, Alex Markuze:
> > 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.
>
> I think you should look at these commits:
>
> ixgbe: add Tx->Rx loopback mode for 82599
>         http://dpdk.org/browse/dpdk/commit/?id=db035925617
> app/testpmd: add loopback topology
>         http://dpdk.org/browse/dpdk/commit/?id=3e2006d6186
>
> --
> Thomas
>

  reply	other threads:[~2014-10-21 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 16:24 Alex Markuze
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 [this message]
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='CAKfHP0VUqUi-XThXjf89u7zGVv++P+r=OaQ5+sOaa_gCEE6ELQ@mail.gmail.com' \
    --to=alex@weka.io \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    /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).