summaryrefslogtreecommitdiff
path: root/.gitignore
diff options
context:
space:
mode:
authorTodd Gamblin <tgamblin@llnl.gov>2016-10-06 00:31:19 -0700
committerTodd Gamblin <tgamblin@llnl.gov>2016-10-11 01:55:33 -0700
commit3d8d8d3644d47c86ed8f77c488355ac1db1c8d42 (patch)
tree319a3f83cf6307235bf09ae2b5b30b719424397c /.gitignore
parenta024c6df954fc43f5d47e788130b9af123bd4cdf (diff)
downloadspack-3d8d8d3644d47c86ed8f77c488355ac1db1c8d42.tar.gz
spack-3d8d8d3644d47c86ed8f77c488355ac1db1c8d42.tar.bz2
spack-3d8d8d3644d47c86ed8f77c488355ac1db1c8d42.tar.xz
spack-3d8d8d3644d47c86ed8f77c488355ac1db1c8d42.zip
Fix bug with lock upgrades.
- Closing and re-opening to upgrade to write will lose all existing read locks on this process. - If we didn't allow ranges, sleeping until no reads would work. - With ranges, we may never be able to take some legal write locks without invalidating all reads. e.g., if a write lock has distinct range from all reads, it should just work, but we'd have to close the file, reopen, and re-take reads. - It's easier to just check whether the file is writable in the first place and open for writing from the start. - Lock now only opens files read-only if we *can't* write them.
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions