Add (optional) argument to pass allow PCI to DPDK #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add (optional) argument
allow
to BESS that is used by DPDK--allow
to indicate what PCI addresses DPDK is allowed to use. This is useful when launching multiple UPF/BESS instances and we know that the UPF only requires 2 VFs/ports in the same machine. However, by default, DPDK will open all ports. So, without this restriction (allow
), a 2nd instance will fail to launch because it will see there is no VFs available to use.The expected input format is:
bessd -f --grpc_url=0.0.0.0:10514
(current format)or
bessd -f --allow="" --grpc_url=0.0.0.0:10514
or
bessd -f --allow=0000:16:01.5,0000:16:01.0 --grpc_url=0.0.0.0:10514
or
bessd -f --allow=0000:16:01.5,0000:16:01.0, --grpc_url=0.0.0.0:10514
(Note the "comma" at the end of the allow value)The changes have been tested deploying the UPF in standalone mode (no
--allow
argument passed) and deploying the UPF as part of AiaB/OnRamp deploying multiple UPF instances and passing the--allow
argument