diff options
author | 2017-06-22 09:51:47 -0400 | |
---|---|---|
committer | 2017-08-16 16:12:05 +0200 | |
commit | f44d2287d2879f50b921e909b2377d6dcba3e251 (patch) | |
tree | 2d892e37dc250abeb5ea43b0329b38c7f22485df /tools/perf/scripts/python/export-to-postgresql.py | |
parent | btrfs: prepare for extensions in compression options (diff) | |
download | wireguard-linux-f44d2287d2879f50b921e909b2377d6dcba3e251.tar.xz wireguard-linux-f44d2287d2879f50b921e909b2377d6dcba3e251.zip |
btrfs: account for pinned bytes in should_alloc_chunk
In a heavy write scenario, we can end up with a large number of pinned bytes.
This can translate into (very) premature ENOSPC because pinned bytes
must be accounted for when allowing a reservation but aren't accounted for
when deciding whether to create a new chunk.
This patch adds the accounting to should_alloc_chunk so that we can
create the chunk.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions