diff options
| author | Nikolay Borisov <nborisov@suse.com> | 2018-06-27 16:38:24 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2018-08-06 13:12:55 +0200 |
| commit | b0132a3be5daf84116833542717ff5692f51640e (patch) | |
| tree | 001e55d66b406327b31e8844f3ecd0c86e046c93 /mm/vmacache.c | |
| parent | 07e21c4dad42be8d2a6b8cd0b98cf8e6931e12fd (diff) | |
| download | linux-b0132a3be5daf84116833542717ff5692f51640e.tar.gz linux-b0132a3be5daf84116833542717ff5692f51640e.tar.bz2 linux-b0132a3be5daf84116833542717ff5692f51640e.zip | |
btrfs: Rename EXTENT_BUFFER_DUMMY to EXTENT_BUFFER_UNMAPPED
EXTENT_BUFFER_DUMMY is an awful name for this flag. Buffers which have
this flag set are not in any way dummy. Rather, they are private in the
sense that are not mapped and linked to the global buffer tree. This
flag has subtle implications to the way free_extent_buffer works for
example, as well as controls whether page->mapping->private_lock is held
during extent_buffer release. Pages for an unmapped buffer cannot be
under io, nor can they be written by a 3rd party so taking the lock is
unnecessary.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
[ EXTENT_BUFFER_UNMAPPED, update changelog ]
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'mm/vmacache.c')
0 files changed, 0 insertions, 0 deletions