-
Notifications
You must be signed in to change notification settings - Fork 164
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
Allow EVE memory limits above 4GB. #4301
Merged
eriknordmark
merged 1 commit into
lf-edge:master
from
OhmSpectator:fix/allow-higher-eve-mem-limits
Sep 30, 2024
Merged
Allow EVE memory limits above 4GB. #4301
eriknordmark
merged 1 commit into
lf-edge:master
from
OhmSpectator:fix/allow-higher-eve-mem-limits
Sep 30, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OhmSpectator
added
bug
Something isn't working
stable
Should be backported to stable release(s)
labels
Sep 27, 2024
Previously, EVE's memory limit was stored in bytes using a uint32 value in the global configuration, limiting the maximum memory to approximately 4GB. This restriction prevented setting higher memory limits necessary for applications like kubevirt. This commit introduces support for specifying the EVE memory limit in mebibytes (MiB) while maintaining backward compatibility with the byte-based configuration. If the byte-based limit is set and valid, it is used; otherwise, the MiB-based limit is applied. This enhancement allows EVE to support memory limits beyond 4GB and ensures accurate memory management, preventing issues in scenarios that require higher memory allocations. Signed-off-by: Nikolay Martyanov <[email protected]>
OhmSpectator
force-pushed
the
fix/allow-higher-eve-mem-limits
branch
from
September 27, 2024 15:44
b6753fd
to
c43ab97
Compare
eriknordmark
approved these changes
Sep 30, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kick off tests in parallel with documentation discussion.
eriknordmark
approved these changes
Sep 30, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Run eden tests
The pull limits, again =( |
This was referenced Sep 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, EVE's memory limit was stored in bytes using a uint32 value in the global configuration, limiting the maximum memory to approximately 4GB. This restriction prevented setting higher memory limits necessary for example for kubevirt. Configuring a memory limit larger than 4GB caused EVE to incorrectly store the value as 0, resulting in inaccurate memory requirement estimations.
This commit changes the memory limit configuration to use mebibytes (MiB) instead of bytes, allowing EVE to support memory limits beyond 4GB.