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

"send: No buffer space available" on EL9 when using Zero-copy #60

Open
marcosfsch opened this issue Apr 6, 2024 · 0 comments
Open

"send: No buffer space available" on EL9 when using Zero-copy #60

marcosfsch opened this issue Apr 6, 2024 · 0 comments

Comments

@marcosfsch
Copy link

marcosfsch commented Apr 6, 2024

I found a strange inconsistency between running neper with -Z on a Alma 9 and Ubuntu 22.04 hosts, both using default kernel.
With default configs both works fine (mtu 1500 and max tcp_wmem 4MB)
But when MSS is above 3444 and max tcp_wmem above 9MB, on Alma 9 "send: No buffer space available" keeps spamming on the client side. On Ubuntu 22.04 it works with no errors.

Example config that works on both OSes: MTU=1500 and net.ipv4.tcp_wmem="4096 16384 4194304"
Example config that gives errors on Alma 9: MTU=4168 and net.ipv4.tcp_wmem="4096 16384 16777216"

My test environment are 2 servers back to back, with the same spec and same Connectx-6 NIC. I'm just dual booting between both OSes to tshoot.
I looked both servers sysctl and NIC configs using ethtool and couldn't find any differences.

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

1 participant