Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add (optional) argument to pass allow PCI to DPDK #60

Merged
merged 1 commit into from
May 17, 2024

Conversation

gab-arrobo
Copy link
Contributor

@gab-arrobo gab-arrobo commented May 16, 2024

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

@gab-arrobo gab-arrobo changed the title Add argument to pass allow PCI to DPDK Add (optional) argument to pass allow PCI to DPDK May 16, 2024
@thakurajayL thakurajayL merged commit 28a4f96 into omec-project:master May 17, 2024
11 checks passed
@gab-arrobo gab-arrobo deleted the limit-ports branch May 17, 2024 01:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants