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

Multicast loopback not working when payload is higher than MTU #234

Open
atik7 opened this issue Jul 23, 2024 · 3 comments
Open

Multicast loopback not working when payload is higher than MTU #234

atik7 opened this issue Jul 23, 2024 · 3 comments

Comments

@atik7
Copy link

atik7 commented Jul 23, 2024

how to receive loopback multicast when payload is bigger than MTU?

EF_MCAST_SEND=3.
EF_MCAST_RECV_HW_LOOP=1.

btw, loopback works only payload is lower than MTU.

@ivatet-amd
Copy link
Contributor

The assumption is that it is NIC X2 Series with the full-feature Firmware variant, multiple Onloaded applications that send and receive the multicast traffic via accelerated sockets, and MTU cannot be changed.

Currently, we have an unresolved ticket, ON-14652, opened for the above configuration and EF_MCAST_RECV_HW_LOOP=1 EF_MCAST_SEND=3 so that it is expected that your Onloaded receiver does not receive loopback fragmented multicast.

Meanwhile, could you try the Onload stack sharing with EF_NAME=foo EF_MCAST_SEND=3 as a workaround? It might work for you.

Further, please email our Support Team at support-nic@amd.com for help with tuning specifically for your application.

@ivatet-amd
Copy link
Contributor

However, with the Onload stack sharing EF_NAME=foo, please be aware that the affected Onloaded applications might interfere with each other in undesirable ways. For instance, they might end up contending for the same Onload stack lock, reducing their overall performance. The Onload User Guide also warns about it at https://docs.amd.com/r/en-US/ug1586-onload-user/Stack-Sharing.

The suggestion to contact our Support Team is still the case.

@atik7
Copy link
Author

atik7 commented Jul 25, 2024

Thank you for the details. Correct, it does work if EF_NAME are same, but this is not we are looking for, we need to support different EF_NAME, is there any priority for ON-14652?

Noted about the support email address,

@atik7 atik7 closed this as completed Jul 25, 2024
@atik7 atik7 reopened this Jul 25, 2024
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

No branches or pull requests

2 participants