aboutsummaryrefslogtreecommitdiff
path: root/fs/btrfs/dev-replace.c
diff options
context:
space:
mode:
authorQu Wenruo <wqu@suse.com>2024-02-17 16:59:49 +1030
committerDavid Sterba <dsterba@suse.com>2024-03-05 17:13:23 +0100
commit8e7e9c672fd810a099dc2ac92a80e8e95cd5b0dc (patch)
tree60a6f6d218ebc78fea0016aae795d72bffb40bbc /fs/btrfs/dev-replace.c
parent621b9ff18c009ed6512df93b63fcf7dbac4cb4e0 (diff)
downloadlinux-8e7e9c672fd810a099dc2ac92a80e8e95cd5b0dc.tar.gz
linux-8e7e9c672fd810a099dc2ac92a80e8e95cd5b0dc.tar.bz2
linux-8e7e9c672fd810a099dc2ac92a80e8e95cd5b0dc.zip
btrfs: subpage: make reader lock utilize bitmap
Currently btrfs_subpage utilizes its atomic member @reader to manage the reader counter. However it is only utilized to prevent the page to be released/unlocked when we still have reads underway. In that use case, we don't really allow multiple readers on the same subpage sector. So here we can introduce a new locked bitmap to represent exactly which subpage range is locked for read. In theory we can remove btrfs_subpage::reader as it's just the set bits of the new locked bitmap. But unfortunately bitmap doesn't provide such handy API yet, so we still keep the reader counter. Signed-off-by: Qu Wenruo <wqu@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/dev-replace.c')
0 files changed, 0 insertions, 0 deletions