You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the intel10g driver, it seems to be possible to get a MAC address table overflow error (core/main.lua:26: MAC address table overflow) if you ever use more than 128 MAC addresses. Even if they are not used simultaneously (e.g., you reconfigure the NIC app repeatedly without reseting the NIC).
Is this behavior ok, or should the driver disable unused MAC addresses after all apps using it are gone? (it does this for VLAN tags and I think it could do the same for MACs) I'm asking because I'm wondering what the behavior should be for intel_mp.
Here's an example script that demonstrates the issue (running it will fail the assertion):
#!../../snabb snsh-- Test mac address allocationlocalbasic_apps=require("apps.basic.basic_apps")
localintel=require("apps.intel.intel_app")
locallib=require("core.lib")
localpciaddr0=lib.getenv("SNABB_PCI_INTEL0")
-- 128 is one more than the 127 limitfori=0, 128dolocalc=config.new()
config.app(c, "nic", intel.driver,
{ pciaddr=pciaddr0,
vmdq=true,
macaddr="00:11:22:33:44:" ..string.format("%02x", i) })
config.app(c, "source", basic_apps.Source)
config.link(c, "source.out0 -> nic.input")
engine.configure(c)
engine.main({ duration=0.01 })
end
Comparatively, it's fine to do the same thing with VLAN tags:
Using the
intel10g
driver, it seems to be possible to get a MAC address table overflow error (core/main.lua:26: MAC address table overflow
) if you ever use more than 128 MAC addresses. Even if they are not used simultaneously (e.g., you reconfigure the NIC app repeatedly without reseting the NIC).Is this behavior ok, or should the driver disable unused MAC addresses after all apps using it are gone? (it does this for VLAN tags and I think it could do the same for MACs) I'm asking because I'm wondering what the behavior should be for
intel_mp
.Here's an example script that demonstrates the issue (running it will fail the assertion):
Comparatively, it's fine to do the same thing with VLAN tags:
The text was updated successfully, but these errors were encountered: