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

Use a non-blocking lock for coordinating memory reporting #785

Merged
merged 2 commits into from
Feb 7, 2025

Conversation

abensonca
Copy link
Collaborator

There's no need for one thread to wait to do memory reporting if another thread is already reporting.

Attempts to acquire a lock - returning false without blocking if this fails.
There's no need for one thread to wait to do memory reporting if another thread is already reporting.
@abensonca abensonca self-assigned this Feb 6, 2025
@abensonca abensonca added enhancement New feature or request optimization labels Feb 6, 2025
Copy link

github-actions bot commented Feb 7, 2025

⚠️ Possible misspelled word 'mallinfo2' in file 'source/utility.memory_reporting.F90'
⚠️ Possible misspelled word 'getpagesize' in file 'source/utility.memory_reporting.F90'
⚠️ Possible misspelled word 'mallinfo2' in file 'source/utility.memory_reporting.F90'
⚠️ Possible misspelled word 'slurm' in file 'source/utility.memory_reporting.F90'

@abensonca abensonca added this pull request to the merge queue Feb 7, 2025
Merged via the queue into master with commit 7ea61e8 Feb 7, 2025
305 checks passed
@abensonca abensonca deleted the featMemoryReportLocking branch February 7, 2025 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request optimization
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant