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

Eio_unix: Allocation warning from sched.ml breaks cram tests #677

Closed
clecat opened this issue Jan 31, 2024 · 2 comments
Closed

Eio_unix: Allocation warning from sched.ml breaks cram tests #677

clecat opened this issue Jan 31, 2024 · 2 comments

Comments

@clecat
Copy link

clecat commented Jan 31, 2024

Context:
When working on moving a project to eio, a warning has started to appear on the CI servers:
eio_linux [WARNING] Failed to allocate 262144 byte fixed buffer

The warning seems to come from the allocation of the fixed uring buffer done for the scheduler here.
This buffer size is calculated with the default values set here and seems quite reasonable.

However my guess is that the shared memory with the kernel allowed by the CI servers for each worker is quite limited to avoid impacting other CI runs.

Issue:
While eio is perfectly able to run without a fixed buffer for it's scheduler, it raises a warning nonetheless, which happens to break some cram tests of our project in which we might want to track our own warnings (hence we cannot simply disable all warning logs).

Question:
Would there be a way for us to disable/not get this warning as an application built over eio ? Maybe by exposing a way to set the log level from the eio_main/eio_linux interface.

Thank you for your time, Gwen

@talex5
Copy link
Collaborator

talex5 commented Jan 31, 2024

It is possible to get the log source from Logs, using Logs.Src.list, and configure the level there.

I'd like to remove the logs dependency completely (only eio_linux is still using it, and only in two places), so I'd prefer not to expose the log source in the API.

@clecat
Copy link
Author

clecat commented Jan 31, 2024

I see thank you for your answer. It would indeed be a bad idea if logs is going to be removed.

I had considered Logs.Src.list but I did not know the extend at which you were using logs within eio.
However with your answer, I'll go for it ! Have a nice day

@clecat clecat closed this as completed Jan 31, 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