Skip to content

DAOS-19292 doc: warn against using PMEM_NO_FLUSH (#18703) - #18948

Open
knard38 wants to merge 1 commit into
release/2.8from
ckochhof/fix/release/2.8/daos-19292/patch-001
Open

DAOS-19292 doc: warn against using PMEM_NO_FLUSH (#18703)#18948
knard38 wants to merge 1 commit into
release/2.8from
ckochhof/fix/release/2.8/daos-19292/patch-001

Conversation

@knard38

@knard38 knard38 commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Description

Replace the note recommending PMEM_NO_FLUSH=1 on ICX systems with an explicit warning against setting it in production. Per PMDK's libpmem(7) documentation, this variable is testing-only; PMDK already detects eADR support automatically via
pmem_has_auto_flush().

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

Replace the note recommending PMEM_NO_FLUSH=1 on ICX systems with
an explicit warning against setting it in production. Per PMDK's
libpmem(7) documentation, this variable is testing-only; PMDK
already detects eADR support automatically via
pmem_has_auto_flush().

Doc-only: true
Signed-off-by: Cedric Koch-Hofer <cedric.koch-hofer@hpe.com>
@knard38 knard38 self-assigned this Aug 27, 2026
@knard38
knard38 requested a review from a team as a code owner August 27, 2026 08:10
@knard38 knard38 added clean-cherry-pick Cherry-pick from another branch that did not require additional edits doc-only Changes only affect documentation, not code approved-to-merge PR has received release branch merge approval labels Aug 27, 2026
@github-actions

Copy link
Copy Markdown

Ticket title is 'Remove unsafe PMEM_NO_FLUSH guidance from performance_tuning.md'
Status is 'Awaiting backport'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-19292

@github-actions github-actions Bot added the priority Ticket has high priority (automatically managed) label Aug 27, 2026
@daltonbohning daltonbohning added the release-2.8.1 Targeted for release 2.8.1 label Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved-to-merge PR has received release branch merge approval clean-cherry-pick Cherry-pick from another branch that did not require additional edits doc-only Changes only affect documentation, not code priority Ticket has high priority (automatically managed) release-2.8.1 Targeted for release 2.8.1

Development

Successfully merging this pull request may close these issues.

2 participants