From: Alex Markuze <alex@weka.io>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] 82599 Ethernet Controller Virtual Function
Date: Sun, 16 Nov 2014 13:08:24 +0200 [thread overview]
Message-ID: <CAKfHP0XFzoVw-GpfWXguQh9HbPJ22agq_d89JCJhLD3rAkyGFQ@mail.gmail.com> (raw)
Hi,
I'm working with a VMware SRIOV with intel 10G nics.
I'm using two virtual functions per VM, mainly because I need loopback
(the LLE(PFVMTXSW[n])
register is not allowing loopback on a VF by default).
After adding a second VF to the VM's I often see issues where no traffic is
passing between the VF's.
Each VM has 4 legs:
1. mgmnt (vmxnet over the onboard 1 GB)- ssh connections
2. data mgmnt (vmxnet over the physical function) - "Trusted interface"
to ping DPDK apps/KNI
3 + 4) VF bound to igbuio - for the application.
The issue I see, is that some VF cannot communicate with other VF's either
same nic or a different Nic. For example two "data mgmnt" vmxnet3
interfaces (not bound to DPDK) cannot see each other.
The only thing that seem to solve it is a VM shutdown (a reboot of a VM
will not help).
Has anyone seen something like this? any suggestions how to debug analyse
what I'm seeing.
reply other threads:[~2014-11-16 10:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAKfHP0XFzoVw-GpfWXguQh9HbPJ22agq_d89JCJhLD3rAkyGFQ@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).