Martin since I'm happy you work with that code base I'd recommend you create a
test setup based on virtio.
You will still be blocked on bug 1559912 for now, but I'm working on that this
week and stil hope to get some upstream support.
I'll reject this bug for the given reasons now, but please ca
I checked the other default disabled drivers.
To all some kind of incompleteness, non-support or being only stubs applies.
It could be said, that the same is true for the virtual ones we enable like
PCAP and XEN.
But there is a major difference in:
- nobody is "buying" the HW for pcap or XEN to t
As an example what I meant to imply here the reason why it is disabled
by default as of now.
commit ce9b8bb8b99877026fcca00fdb253fa3ec3a7e06
Author: Thomas Monjalon
Date: Tue Jul 28 18:22:39 2015 +0200
config: disable bnx2x driver
This driver has too many issues:
- too big
Hi Thiago,
you were busy weren't you :-)
Thanks your further experiments and reports - I'll try to refer all the open
points.
Trying to summarize:
1. The vfio grouping issue is not a bug, just the vfio setup being more complex
in general. But you already handled that for your setup - great.
But
Since I consider the extra PMDs kind of "unsupported" upstream I have to
rate it low for now.
** Changed in: dpdk (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.lau
Yeah, I am unable to rebuild OpenvSwitch against my libdpdk-dev...
:-(
I can easily rebuild it, using Ubuntu's libdpdk-dev but, after enabling
BNX2X_PMD, OpenvSwitch doesn't build, I'm seeing the following error:
-
apt source openvswitch
cd openvswitch-2.5.0
dpkg-buildpackage -rfakeroot -uc -us
Mmmm... Might not be a hugetable memory, double checked everything.
I'm thinking about the following error:
-
kernel: ovs-vswitchd[3793]: segfault at c80086e430 ip 7f0a4f222b26 sp
7ffce3539190 error 4 in libdpdk.so.0[7f0a4f1ff000+22f000]
-
Since I repackaged DPDK to enable BNX2X with PM
Right,
Just for the record, for the first time ever, I'm seeing a different
message here:
---
# ovs-vsctl show
b70c1e0a-20d7-4bdb-98db-467330
After digging into DPDK source code, I found this:
--
cd ~/sources/dpdk/dpdk-2.2.0/drivers/net/
grep -ri \/firmware *
bnx2x/bnx2x.c:#define FW_NAME_57711 "/lib/firmware/bnx2x/bnx2x-e1h-7.2.51.0.fw"
bnx2x/bnx2x.c:#define FW_NAME_57810 "/lib/firmware/bnx2x/bnx2x-e2-7.2.51.0.fw"
--
However, those
So,
I managed to include all NICs under the same IOMMU Group, like this:
---
dpdk_nic_bind --status
Network devices using DPDK-compatible driver
:01:00.0 'NetXtreme II BCM57800 1/10 Gigabit Ethernet' drv=vfio-pci
unused=bnx2x
:01:00.1 'NetXt
10 matches
Mail list logo
