From: Alex Markuze <alex@weka.io>
To: "Liang, Cunming" <cunming.liang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] nic loopback
Date: Tue, 21 Oct 2014 18:16:16 +0300 [thread overview]
Message-ID: <CAKfHP0VfQWAo3nQSW_Li3V7OL3kxv=s5N_ZdNEC3qfuc9gm1Bg@mail.gmail.com> (raw)
In-Reply-To: <D0158A423229094DA7ABF71CF2FA0DA31184EBD1@shsmsx102.ccr.corp.intel.com>
How can I set/query this bit (LLE(PFVMTXSW[n]), intel 82599 ) on ESX, or
any other friendlier environment like Linux?
On Tue, Oct 21, 2014 at 4:18 AM, Liang, Cunming <cunming.liang@intel.com>
wrote:
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Markuze
> > Sent: Tuesday, October 21, 2014 12:24 AM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] nic loopback
> >
> > 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.
> >
> [Liang, Cunming] You could have a check on register LLE(PFVMTXSW[n]).
> Which allow an individual pool to be able to send traffic and have it
> loopback to itself.
> >
> > Thanks.
>
next prev parent reply other threads:[~2014-10-21 15:08 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 [this message]
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='CAKfHP0VfQWAo3nQSW_Li3V7OL3kxv=s5N_ZdNEC3qfuc9gm1Bg@mail.gmail.com' \
--to=alex@weka.io \
--cc=cunming.liang@intel.com \
--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).