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

DAOS-16877 client: implement utilities for shared memory #15613

Open
wants to merge 4 commits into
base: feature/dfs_dcache
Choose a base branch
from

Conversation

wiliamhuang
Copy link
Contributor

Features: shm

  1. use tlsf as memory allocator
  2. shared memory create/destroy
  3. robust mutex in shared memory
  4. hash table in shared memory

Required-githooks: true
Skipped-githooks: codespell

Before requesting gatekeeper:

  • Two review approvals and any prior change requests have been resolved.
  • Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
  • Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
  • Commit messages follows the guidelines outlined here.
  • Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

  • You are the appropriate gatekeeper to be landing the patch.
  • The PR has 2 reviews by people familiar with the code, including appropriate owners.
  • Githooks were used. If not, request that user install them and check copyright dates.
  • Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
  • All builds have passed. Check non-required builds for any new compiler warnings.
  • Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
  • If applicable, the PR has addressed any potential version compatibility issues.
  • Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
  • Extra checks if forced landing is requested
    • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
    • No new NLT or valgrind warnings. Check the classic view.
    • Quick-build or Quick-functional is not used.
  • Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

Features: shm

1. use tlsf as memory allocator
2. shared memory create/destroy
3. robust mutex in shared memory
4. hash table in shared memory

Required-githooks: true
Skipped-githooks: codespell

Signed-off-by: Lei Huang <lei.huang@intel.com>
Copy link

Ticket title is 'To implement node-wise caching with shared memory '
Status is 'Open'
https://daosio.atlassian.net/browse/DAOS-16877

@daosbuild1
Copy link
Collaborator

Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15613/1/execution/node/1210/log

Features: shm

Required-githooks: true
Skipped-githooks: codespell

Signed-off-by: Lei Huang <lei.huang@intel.com>
…hm_mutex

Features: shm

Required-githooks: true
Skipped-githooks: codespell

Signed-off-by: Lei Huang <lei.huang@intel.com>
Features: shm

Required-githooks: true
Skipped-githooks: codespell

Signed-off-by: Lei Huang <lei.huang@intel.com>
@wiliamhuang wiliamhuang marked this pull request as ready for review December 23, 2024 15:15
@wiliamhuang wiliamhuang requested review from a team as code owners December 23, 2024 15:15
@wiliamhuang
Copy link
Contributor Author

Some component (e.g., hash table record reference count) will be revised later when we add more use cases.

@wiliamhuang
Copy link
Contributor Author

Currently we use tlsf memory allocator. It will be replaced by our own allocator in future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants