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

Failed to memadvise buffer to kernel #28

Closed
robinchrist opened this issue Jun 1, 2024 · 3 comments
Closed

Failed to memadvise buffer to kernel #28

robinchrist opened this issue Jun 1, 2024 · 3 comments

Comments

@robinchrist
Copy link

[2024-06-01T17:19:35Z ERROR breakwater::server] Failed to memadvise buffer to kernel, propably having some performance degration: InvalidRange
[2024-06-01T17:19:35Z ERROR breakwater::server] Failed to memadvise buffer to kernel, propably having some performance degration: NullAddress

bbef8cf

@sbernauer
Copy link
Owner

Thanks for reporting this!

I now had the time to look into this issue and I'm a bit confused how this can fail, as we allocate the memory directly above, so I don't see any reason the pointer should be invalid or even null.

However, the error is only printed and the thread continues processing the data send. The worst thing that should happen is a minimal performance degradation.

I don't see how this situation can be improved in any way, would you be ok with closing this for now?

@robinchrist
Copy link
Author

Yep sure, thanks for looking into it.
Just something we noticed while running Pixelflut with > 100Gbit/s continuous (real world performance) at GPN22.

Maybe it should be noted in the README that this is known?

@sbernauer
Copy link
Owner

Sure, raised a PR for that, happy about review! #29

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