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

nm_tx_pending is always true (ixgbe) #621

Open
ds-j-ot opened this issue Jun 4, 2019 · 3 comments
Open

nm_tx_pending is always true (ixgbe) #621

ds-j-ot opened this issue Jun 4, 2019 · 3 comments

Comments

@ds-j-ot
Copy link

ds-j-ot commented Jun 4, 2019

Regarding appneta/tcpreplay#560

Using tcpreplay with netmap (current master, ixgbe out-of-tree driver), nm_tx_pending always reports true even when all packets are sent.

This does not occur with igb.

@ds-j-ot
Copy link
Author

ds-j-ot commented Jun 4, 2019

The same problem occurs with other driver versions and also using --no-ext-drivers.

@ds-j-ot
Copy link
Author

ds-j-ot commented Jun 13, 2019

Any idea?

@vmaffione
Copy link
Collaborator

How do you tell that packets where transmitted and the transmission was notified to netmap? Can you report the values of ring->head, ring->cur, and ring->tail when this happens? What are the values immediately after opening the netmap port, before performing any operation? What happens if you call ioctl(NIOCTXSYNC) a second after the apparent stall happens?

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