From: "Zhu, Heqing" <heqing.zhu@intel.com>
To: "Liang, Cunming" <cunming.liang@intel.com>,
"alex@weka.io" <alex@weka.io>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] FW: nic loopback
Date: Wed, 22 Oct 2014 04:37:50 +0000 [thread overview]
Message-ID: <CAD16F236028A64DBBC0158B1636EA4510F80BE1@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <D0158A423229094DA7ABF71CF2FA0DA311850533@shsmsx102.ccr.corp.intel.com>
One line comment inline.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Liang, Cunming
> Sent: Tuesday, October 21, 2014 8:33 PM
> To: Alex Markuze
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] nic loopback
>
> It’s a pain VF can’t set the register directly.
> As kernel ixgbe don’t support to set the value, I’m afraid you have to modify
> kernel ixgbe.
> If your purpose is mainly for testing purpose.
> One option is you can just set the register bit value to full 1 during device
> initialization.
> Another option is you can choose to use DPDK as host PF.
> Running testpmd in host, and set such register by interactive command line.
>
> Ideally it’s better to add a kind of VF to PF mailbox message.
> Host PF delegate VF to enable the local pool loopback.
> So during runtime, VF can proactive to enable/disable the ability.
[heqing] Such a proposal has been discussed a few times, but the kernel driver does not accept this due to the security concern.
>
>
> From: Alex Markuze [mailto:alex@weka.io]
> Sent: Tuesday, October 21, 2014 11:16 PM
> To: Liang, Cunming
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] nic loopback
>
> 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<mailto:cunming.liang@intel.com>> wrote:
>
>
> > -----Original Message-----
> > From: dev
> [mailto:dev-bounces@dpdk.org<mailto:dev-bounces@dpdk.org>]
> > On Behalf Of Alex Markuze
> > Sent: Tuesday, October 21, 2014 12:24 AM
> > To: dev@dpdk.org<mailto: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-22 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 16:24 [dpdk-dev] " 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 ` Zhu, Heqing [this message]
2014-10-22 7:42 ` [dpdk-dev] FW: " 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=CAD16F236028A64DBBC0158B1636EA4510F80BE1@SHSMSX104.ccr.corp.intel.com \
--to=heqing.zhu@intel.com \
--cc=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).