-
Notifications
You must be signed in to change notification settings - Fork 246
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
Additional clarification about %vmeff exceeding 100% in newer kernels #1782
Merged
sounix000
merged 4 commits into
main
from
ssarkar/DOCTEAM-1252-vmeff-clarifications-newer-kernels
Jan 21, 2025
Merged
Additional clarification about %vmeff exceeding 100% in newer kernels #1782
sounix000
merged 4 commits into
main
from
ssarkar/DOCTEAM-1252-vmeff-clarifications-newer-kernels
Jan 21, 2025
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
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.
Hi, please see just a couple of nits here. Thanks!
dariavladykina
approved these changes
Nov 27, 2024
taroth21
reviewed
Dec 2, 2024
taroth21
approved these changes
Dec 9, 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.
LGTM, many thanks!
sounix000
force-pushed
the
ssarkar/DOCTEAM-1252-vmeff-clarifications-newer-kernels
branch
from
January 21, 2025 15:41
da215c9
to
0f8408e
Compare
sounix000
added a commit
that referenced
this pull request
Jan 21, 2025
…#1782) * note on vmeff clarification * Editorial fixes as per Daria's suggestion * Minor typo fix * Modified content based on Tanja's feedback
sounix000
added a commit
that referenced
this pull request
Jan 21, 2025
…#1782) * note on vmeff clarification * Editorial fixes as per Daria's suggestion * Minor typo fix * Modified content based on Tanja's feedback
sounix000
added a commit
that referenced
this pull request
Jan 21, 2025
…#1782) * note on vmeff clarification * Editorial fixes as per Daria's suggestion * Minor typo fix * Modified content based on Tanja's feedback
sounix000
added a commit
that referenced
this pull request
Jan 21, 2025
…#1782) * note on vmeff clarification * Editorial fixes as per Daria's suggestion * Minor typo fix * Modified content based on Tanja's feedback
sounix000
deleted the
ssarkar/DOCTEAM-1252-vmeff-clarifications-newer-kernels
branch
January 21, 2025 16:08
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.
PR creator: Description
Clarify how to interpret and act when
%vmeff
value exceeds 100% as part ofsar -B
report, because it doesn't make sense under normal circumstances that the kernel reclaims more virtual memory pages than it scans.Preview
PR creator: Are there any relevant issues/feature requests?
PR creator: Which product versions do the changes apply to?
When opening a PR, check all versions of the documentation that your PR applies to.
SLE 15/openSUSE Leap 15.x
main
, no backport necessary): 3e2a2c2SLE 12
PR reviewer only: Have all backports been applied?
The doc team member merging your PR will take care of backporting to older documents.
When opening a PR, do not set the following check box.