2008-01-25 00:13:08 +03:00
# ifndef __EXTENTIO__
# define __EXTENTIO__
# include <linux/rbtree.h>
2015-10-12 07:08:16 +03:00
# include "ulist.h"
2008-01-25 00:13:08 +03:00
/* bits for the extent state */
2015-01-14 21:52:13 +03:00
# define EXTENT_DIRTY (1U << 0)
# define EXTENT_WRITEBACK (1U << 1)
# define EXTENT_UPTODATE (1U << 2)
# define EXTENT_LOCKED (1U << 3)
# define EXTENT_NEW (1U << 4)
# define EXTENT_DELALLOC (1U << 5)
# define EXTENT_DEFRAG (1U << 6)
# define EXTENT_BOUNDARY (1U << 9)
# define EXTENT_NODATASUM (1U << 10)
# define EXTENT_DO_ACCOUNTING (1U << 11)
# define EXTENT_FIRST_DELALLOC (1U << 12)
# define EXTENT_NEED_WAIT (1U << 13)
# define EXTENT_DAMAGED (1U << 14)
# define EXTENT_NORESERVE (1U << 15)
2015-10-12 11:05:40 +03:00
# define EXTENT_QGROUP_RESERVED (1U << 16)
btrfs: update btrfs_space_info's bytes_may_use timely
This patch can fix some false ENOSPC errors, below test script can
reproduce one false ENOSPC error:
#!/bin/bash
dd if=/dev/zero of=fs.img bs=$((1024*1024)) count=128
dev=$(losetup --show -f fs.img)
mkfs.btrfs -f -M $dev
mkdir /tmp/mntpoint
mount $dev /tmp/mntpoint
cd /tmp/mntpoint
xfs_io -f -c "falloc 0 $((64*1024*1024))" testfile
Above script will fail for ENOSPC reason, but indeed fs still has free
space to satisfy this request. Please see call graph:
btrfs_fallocate()
|-> btrfs_alloc_data_chunk_ondemand()
| bytes_may_use += 64M
|-> btrfs_prealloc_file_range()
|-> btrfs_reserve_extent()
|-> btrfs_add_reserved_bytes()
| alloc_type is RESERVE_ALLOC_NO_ACCOUNT, so it does not
| change bytes_may_use, and bytes_reserved += 64M. Now
| bytes_may_use + bytes_reserved == 128M, which is greater
| than btrfs_space_info's total_bytes, false enospc occurs.
| Note, the bytes_may_use decrease operation will be done in
| end of btrfs_fallocate(), which is too late.
Here is another simple case for buffered write:
CPU 1 | CPU 2
|
|-> cow_file_range() |-> __btrfs_buffered_write()
|-> btrfs_reserve_extent() | |
| | |
| | |
| ..... | |-> btrfs_check_data_free_space()
| |
| |
|-> extent_clear_unlock_delalloc() |
In CPU 1, btrfs_reserve_extent()->find_free_extent()->
btrfs_add_reserved_bytes() do not decrease bytes_may_use, the decrease
operation will be delayed to be done in extent_clear_unlock_delalloc().
Assume in this case, btrfs_reserve_extent() reserved 128MB data, CPU2's
btrfs_check_data_free_space() tries to reserve 100MB data space.
If
100MB > data_sinfo->total_bytes - data_sinfo->bytes_used -
data_sinfo->bytes_reserved - data_sinfo->bytes_pinned -
data_sinfo->bytes_readonly - data_sinfo->bytes_may_use
btrfs_check_data_free_space() will try to allcate new data chunk or call
btrfs_start_delalloc_roots(), or commit current transaction in order to
reserve some free space, obviously a lot of work. But indeed it's not
necessary as long as decreasing bytes_may_use timely, we still have
free space, decreasing 128M from bytes_may_use.
To fix this issue, this patch chooses to update bytes_may_use for both
data and metadata in btrfs_add_reserved_bytes(). For compress path, real
extent length may not be equal to file content length, so introduce a
ram_bytes argument for btrfs_reserve_extent(), find_free_extent() and
btrfs_add_reserved_bytes(), it's becasue bytes_may_use is increased by
file content length. Then compress path can update bytes_may_use
correctly. Also now we can discard RESERVE_ALLOC_NO_ACCOUNT, RESERVE_ALLOC
and RESERVE_FREE.
As we know, usually EXTENT_DO_ACCOUNTING is used for error path. In
run_delalloc_nocow(), for inode marked as NODATACOW or extent marked as
PREALLOC, we also need to update bytes_may_use, but can not pass
EXTENT_DO_ACCOUNTING, because it also clears metadata reservation, so
here we introduce EXTENT_CLEAR_DATA_RESV flag to indicate btrfs_clear_bit_hook()
to update btrfs_space_info's bytes_may_use.
Meanwhile __btrfs_prealloc_file_range() will call
btrfs_free_reserved_data_space() internally for both sucessful and failed
path, btrfs_prealloc_file_range()'s callers does not need to call
btrfs_free_reserved_data_space() any more.
Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Chris Mason <clm@fb.com>
2016-07-25 10:51:40 +03:00
# define EXTENT_CLEAR_DATA_RESV (1U << 17)
2015-01-14 21:52:13 +03:00
# define EXTENT_IOBITS (EXTENT_LOCKED | EXTENT_WRITEBACK)
# define EXTENT_CTLBITS (EXTENT_DO_ACCOUNTING | EXTENT_FIRST_DELALLOC)
2008-01-25 00:13:08 +03:00
2010-12-17 09:21:50 +03:00
/*
* flags for bio submission . The high bits indicate the compression
* type for this bio
*/
Btrfs: Add zlib compression support
This is a large change for adding compression on reading and writing,
both for inline and regular extents. It does some fairly large
surgery to the writeback paths.
Compression is off by default and enabled by mount -o compress. Even
when the -o compress mount option is not used, it is possible to read
compressed extents off the disk.
If compression for a given set of pages fails to make them smaller, the
file is flagged to avoid future compression attempts later.
* While finding delalloc extents, the pages are locked before being sent down
to the delalloc handler. This allows the delalloc handler to do complex things
such as cleaning the pages, marking them writeback and starting IO on their
behalf.
* Inline extents are inserted at delalloc time now. This allows us to compress
the data before inserting the inline extent, and it allows us to insert
an inline extent that spans multiple pages.
* All of the in-memory extent representations (extent_map.c, ordered-data.c etc)
are changed to record both an in-memory size and an on disk size, as well
as a flag for compression.
From a disk format point of view, the extent pointers in the file are changed
to record the on disk size of a given extent and some encoding flags.
Space in the disk format is allocated for compression encoding, as well
as encryption and a generic 'other' field. Neither the encryption or the
'other' field are currently used.
In order to limit the amount of data read for a single random read in the
file, the size of a compressed extent is limited to 128k. This is a
software only limit, the disk format supports u64 sized compressed extents.
In order to limit the ram consumed while processing extents, the uncompressed
size of a compressed extent is limited to 256k. This is a software only limit
and will be subject to tuning later.
Checksumming is still done on compressed extents, and it is done on the
uncompressed version of the data. This way additional encodings can be
layered on without having to figure out which encoding to checksum.
Compression happens at delalloc time, which is basically singled threaded because
it is usually done by a single pdflush thread. This makes it tricky to
spread the compression load across all the cpus on the box. We'll have to
look at parallel pdflush walks of dirty inodes at a later time.
Decompression is hooked into readpages and it does spread across CPUs nicely.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2008-10-29 21:49:59 +03:00
# define EXTENT_BIO_COMPRESSED 1
2012-09-25 22:25:58 +04:00
# define EXTENT_BIO_TREE_LOG 2
2010-12-17 09:21:50 +03:00
# define EXTENT_BIO_FLAG_SHIFT 16
Btrfs: Add zlib compression support
This is a large change for adding compression on reading and writing,
both for inline and regular extents. It does some fairly large
surgery to the writeback paths.
Compression is off by default and enabled by mount -o compress. Even
when the -o compress mount option is not used, it is possible to read
compressed extents off the disk.
If compression for a given set of pages fails to make them smaller, the
file is flagged to avoid future compression attempts later.
* While finding delalloc extents, the pages are locked before being sent down
to the delalloc handler. This allows the delalloc handler to do complex things
such as cleaning the pages, marking them writeback and starting IO on their
behalf.
* Inline extents are inserted at delalloc time now. This allows us to compress
the data before inserting the inline extent, and it allows us to insert
an inline extent that spans multiple pages.
* All of the in-memory extent representations (extent_map.c, ordered-data.c etc)
are changed to record both an in-memory size and an on disk size, as well
as a flag for compression.
From a disk format point of view, the extent pointers in the file are changed
to record the on disk size of a given extent and some encoding flags.
Space in the disk format is allocated for compression encoding, as well
as encryption and a generic 'other' field. Neither the encryption or the
'other' field are currently used.
In order to limit the amount of data read for a single random read in the
file, the size of a compressed extent is limited to 128k. This is a
software only limit, the disk format supports u64 sized compressed extents.
In order to limit the ram consumed while processing extents, the uncompressed
size of a compressed extent is limited to 256k. This is a software only limit
and will be subject to tuning later.
Checksumming is still done on compressed extents, and it is done on the
uncompressed version of the data. This way additional encodings can be
layered on without having to figure out which encoding to checksum.
Compression happens at delalloc time, which is basically singled threaded because
it is usually done by a single pdflush thread. This makes it tricky to
spread the compression load across all the cpus on the box. We'll have to
look at parallel pdflush walks of dirty inodes at a later time.
Decompression is hooked into readpages and it does spread across CPUs nicely.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2008-10-29 21:49:59 +03:00
Btrfs: Change btree locking to use explicit blocking points
Most of the btrfs metadata operations can be protected by a spinlock,
but some operations still need to schedule.
So far, btrfs has been using a mutex along with a trylock loop,
most of the time it is able to avoid going for the full mutex, so
the trylock loop is a big performance gain.
This commit is step one for getting rid of the blocking locks entirely.
btrfs_tree_lock takes a spinlock, and the code explicitly switches
to a blocking lock when it starts an operation that can schedule.
We'll be able get rid of the blocking locks in smaller pieces over time.
Tracing allows us to find the most common cause of blocking, so we
can start with the hot spots first.
The basic idea is:
btrfs_tree_lock() returns with the spin lock held
btrfs_set_lock_blocking() sets the EXTENT_BUFFER_BLOCKING bit in
the extent buffer flags, and then drops the spin lock. The buffer is
still considered locked by all of the btrfs code.
If btrfs_tree_lock gets the spinlock but finds the blocking bit set, it drops
the spin lock and waits on a wait queue for the blocking bit to go away.
Much of the code that needs to set the blocking bit finishes without actually
blocking a good percentage of the time. So, an adaptive spin is still
used against the blocking bit to avoid very high context switch rates.
btrfs_clear_lock_blocking() clears the blocking bit and returns
with the spinlock held again.
btrfs_tree_unlock() can be called on either blocking or spinning locks,
it does the right thing based on the blocking bit.
ctree.c has a helper function to set/clear all the locked buffers in a
path as blocking.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-02-04 17:25:08 +03:00
/* these are bit numbers for test/set bit */
# define EXTENT_BUFFER_UPTODATE 0
2009-03-13 18:00:37 +03:00
# define EXTENT_BUFFER_DIRTY 2
2011-03-16 20:42:43 +03:00
# define EXTENT_BUFFER_CORRUPT 3
2011-05-23 16:25:41 +04:00
# define EXTENT_BUFFER_READAHEAD 4 /* this got triggered by readahead */
2012-03-10 01:01:49 +04:00
# define EXTENT_BUFFER_TREE_REF 5
# define EXTENT_BUFFER_STALE 6
2012-03-13 17:38:00 +04:00
# define EXTENT_BUFFER_WRITEBACK 7
Btrfs: be aware of btree inode write errors to avoid fs corruption
While we have a transaction ongoing, the VM might decide at any time
to call btree_inode->i_mapping->a_ops->writepages(), which will start
writeback of dirty pages belonging to btree nodes/leafs. This call
might return an error or the writeback might finish with an error
before we attempt to commit the running transaction. If this happens,
we might have no way of knowing that such error happened when we are
committing the transaction - because the pages might no longer be
marked dirty nor tagged for writeback (if a subsequent modification
to the extent buffer didn't happen before the transaction commit) which
makes filemap_fdata[write|wait]_range unable to find such pages (even
if they're marked with SetPageError).
So if this happens we must abort the transaction, otherwise we commit
a super block with btree roots that point to btree nodes/leafs whose
content on disk is invalid - either garbage or the content of some
node/leaf from a past generation that got cowed or deleted and is no
longer valid (for this later case we end up getting error messages like
"parent transid verify failed on 10826481664 wanted 25748 found 29562"
when reading btree nodes/leafs from disk).
Note that setting and checking AS_EIO/AS_ENOSPC in the btree inode's
i_mapping would not be enough because we need to distinguish between
log tree extents (not fatal) vs non-log tree extents (fatal) and
because the next call to filemap_fdatawait_range() will catch and clear
such errors in the mapping - and that call might be from a log sync and
not from a transaction commit, which means we would not know about the
error at transaction commit time. Also, checking for the eb flag
EXTENT_BUFFER_IOERR at transaction commit time isn't done and would
not be completely reliable, as the eb might be removed from memory and
read back when trying to get it, which clears that flag right before
reading the eb's pages from disk, making us not know about the previous
write error.
Using the new 3 flags for the btree inode also makes us achieve the
goal of AS_EIO/AS_ENOSPC when writepages() returns success, started
writeback for all dirty pages and before filemap_fdatawait_range() is
called, the writeback for all dirty pages had already finished with
errors - because we were not using AS_EIO/AS_ENOSPC,
filemap_fdatawait_range() would return success, as it could not know
that writeback errors happened (the pages were no longer tagged for
writeback).
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Chris Mason <clm@fb.com>
2014-09-26 15:25:56 +04:00
# define EXTENT_BUFFER_READ_ERR 8 /* read IO error */
2012-05-16 19:00:02 +04:00
# define EXTENT_BUFFER_DUMMY 9
2013-12-13 19:41:51 +04:00
# define EXTENT_BUFFER_IN_TREE 10
Btrfs: be aware of btree inode write errors to avoid fs corruption
While we have a transaction ongoing, the VM might decide at any time
to call btree_inode->i_mapping->a_ops->writepages(), which will start
writeback of dirty pages belonging to btree nodes/leafs. This call
might return an error or the writeback might finish with an error
before we attempt to commit the running transaction. If this happens,
we might have no way of knowing that such error happened when we are
committing the transaction - because the pages might no longer be
marked dirty nor tagged for writeback (if a subsequent modification
to the extent buffer didn't happen before the transaction commit) which
makes filemap_fdata[write|wait]_range unable to find such pages (even
if they're marked with SetPageError).
So if this happens we must abort the transaction, otherwise we commit
a super block with btree roots that point to btree nodes/leafs whose
content on disk is invalid - either garbage or the content of some
node/leaf from a past generation that got cowed or deleted and is no
longer valid (for this later case we end up getting error messages like
"parent transid verify failed on 10826481664 wanted 25748 found 29562"
when reading btree nodes/leafs from disk).
Note that setting and checking AS_EIO/AS_ENOSPC in the btree inode's
i_mapping would not be enough because we need to distinguish between
log tree extents (not fatal) vs non-log tree extents (fatal) and
because the next call to filemap_fdatawait_range() will catch and clear
such errors in the mapping - and that call might be from a log sync and
not from a transaction commit, which means we would not know about the
error at transaction commit time. Also, checking for the eb flag
EXTENT_BUFFER_IOERR at transaction commit time isn't done and would
not be completely reliable, as the eb might be removed from memory and
read back when trying to get it, which clears that flag right before
reading the eb's pages from disk, making us not know about the previous
write error.
Using the new 3 flags for the btree inode also makes us achieve the
goal of AS_EIO/AS_ENOSPC when writepages() returns success, started
writeback for all dirty pages and before filemap_fdatawait_range() is
called, the writeback for all dirty pages had already finished with
errors - because we were not using AS_EIO/AS_ENOSPC,
filemap_fdatawait_range() would return success, as it could not know
that writeback errors happened (the pages were no longer tagged for
writeback).
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Chris Mason <clm@fb.com>
2014-09-26 15:25:56 +04:00
# define EXTENT_BUFFER_WRITE_ERR 11 /* write IO error */
Btrfs: Change btree locking to use explicit blocking points
Most of the btrfs metadata operations can be protected by a spinlock,
but some operations still need to schedule.
So far, btrfs has been using a mutex along with a trylock loop,
most of the time it is able to avoid going for the full mutex, so
the trylock loop is a big performance gain.
This commit is step one for getting rid of the blocking locks entirely.
btrfs_tree_lock takes a spinlock, and the code explicitly switches
to a blocking lock when it starts an operation that can schedule.
We'll be able get rid of the blocking locks in smaller pieces over time.
Tracing allows us to find the most common cause of blocking, so we
can start with the hot spots first.
The basic idea is:
btrfs_tree_lock() returns with the spin lock held
btrfs_set_lock_blocking() sets the EXTENT_BUFFER_BLOCKING bit in
the extent buffer flags, and then drops the spin lock. The buffer is
still considered locked by all of the btrfs code.
If btrfs_tree_lock gets the spinlock but finds the blocking bit set, it drops
the spin lock and waits on a wait queue for the blocking bit to go away.
Much of the code that needs to set the blocking bit finishes without actually
blocking a good percentage of the time. So, an adaptive spin is still
used against the blocking bit to avoid very high context switch rates.
btrfs_clear_lock_blocking() clears the blocking bit and returns
with the spinlock held again.
btrfs_tree_unlock() can be called on either blocking or spinning locks,
it does the right thing based on the blocking bit.
ctree.c has a helper function to set/clear all the locked buffers in a
path as blocking.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-02-04 17:25:08 +03:00
2017-02-10 18:41:05 +03:00
/* these are flags for __process_pages_contig */
2013-07-29 19:20:47 +04:00
# define PAGE_UNLOCK (1 << 0)
# define PAGE_CLEAR_DIRTY (1 << 1)
# define PAGE_SET_WRITEBACK (1 << 2)
# define PAGE_END_WRITEBACK (1 << 3)
# define PAGE_SET_PRIVATE2 (1 << 4)
2014-10-07 01:14:22 +04:00
# define PAGE_SET_ERROR (1 << 5)
2017-02-10 18:41:05 +03:00
# define PAGE_LOCK (1 << 6)
2009-10-08 19:27:10 +04:00
2008-01-25 00:13:08 +03:00
/*
* page - > private values . Every page that is controlled by the extent
* map has page - > private set to one .
*/
# define EXTENT_PAGE_PRIVATE 1
2016-09-23 03:24:20 +03:00
/*
* The extent buffer bitmap operations are done with byte granularity instead of
* word granularity for two reasons :
* 1. The bitmaps must be little - endian on disk .
* 2. Bitmap items are not guaranteed to be aligned to a word and therefore a
* single word in a bitmap may straddle two pages in the extent buffer .
*/
# define BIT_BYTE(nr) ((nr) / BITS_PER_BYTE)
# define BYTE_MASK ((1 << BITS_PER_BYTE) - 1)
# define BITMAP_FIRST_BYTE_MASK(start) \
( ( BYTE_MASK < < ( ( start ) & ( BITS_PER_BYTE - 1 ) ) ) & BYTE_MASK )
# define BITMAP_LAST_BYTE_MASK(nbits) \
( BYTE_MASK > > ( - ( nbits ) & ( BITS_PER_BYTE - 1 ) ) )
static inline int le_test_bit ( int nr , const u8 * addr )
{
return 1U & ( addr [ BIT_BYTE ( nr ) ] > > ( nr & ( BITS_PER_BYTE - 1 ) ) ) ;
}
extern void le_bitmap_set ( u8 * map , unsigned int start , int len ) ;
extern void le_bitmap_clear ( u8 * map , unsigned int start , int len ) ;
2008-01-29 17:59:12 +03:00
struct extent_state ;
2012-03-27 05:57:36 +04:00
struct btrfs_root ;
2013-07-25 15:22:34 +04:00
struct btrfs_io_bio ;
2016-02-11 15:24:13 +03:00
struct io_failure_record ;
2008-01-29 17:59:12 +03:00
2016-06-05 22:31:54 +03:00
typedef int ( extent_submit_bio_hook_t ) ( struct inode * inode , struct bio * bio ,
int mirror_num , unsigned long bio_flags ,
u64 bio_offset ) ;
2008-01-25 00:13:08 +03:00
struct extent_io_ops {
Btrfs: Add zlib compression support
This is a large change for adding compression on reading and writing,
both for inline and regular extents. It does some fairly large
surgery to the writeback paths.
Compression is off by default and enabled by mount -o compress. Even
when the -o compress mount option is not used, it is possible to read
compressed extents off the disk.
If compression for a given set of pages fails to make them smaller, the
file is flagged to avoid future compression attempts later.
* While finding delalloc extents, the pages are locked before being sent down
to the delalloc handler. This allows the delalloc handler to do complex things
such as cleaning the pages, marking them writeback and starting IO on their
behalf.
* Inline extents are inserted at delalloc time now. This allows us to compress
the data before inserting the inline extent, and it allows us to insert
an inline extent that spans multiple pages.
* All of the in-memory extent representations (extent_map.c, ordered-data.c etc)
are changed to record both an in-memory size and an on disk size, as well
as a flag for compression.
From a disk format point of view, the extent pointers in the file are changed
to record the on disk size of a given extent and some encoding flags.
Space in the disk format is allocated for compression encoding, as well
as encryption and a generic 'other' field. Neither the encryption or the
'other' field are currently used.
In order to limit the amount of data read for a single random read in the
file, the size of a compressed extent is limited to 128k. This is a
software only limit, the disk format supports u64 sized compressed extents.
In order to limit the ram consumed while processing extents, the uncompressed
size of a compressed extent is limited to 256k. This is a software only limit
and will be subject to tuning later.
Checksumming is still done on compressed extents, and it is done on the
uncompressed version of the data. This way additional encodings can be
layered on without having to figure out which encoding to checksum.
Compression happens at delalloc time, which is basically singled threaded because
it is usually done by a single pdflush thread. This makes it tricky to
spread the compression load across all the cpus on the box. We'll have to
look at parallel pdflush walks of dirty inodes at a later time.
Decompression is hooked into readpages and it does spread across CPUs nicely.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2008-10-29 21:49:59 +03:00
int ( * fill_delalloc ) ( struct inode * inode , struct page * locked_page ,
2008-11-07 06:02:51 +03:00
u64 start , u64 end , int * page_started ,
unsigned long * nr_written ) ;
2008-07-17 20:53:51 +04:00
int ( * writepage_start_hook ) ( struct page * page , u64 start , u64 end ) ;
2008-04-16 19:14:51 +04:00
extent_submit_bio_hook_t * submit_bio_hook ;
2016-06-05 22:31:54 +03:00
int ( * merge_bio_hook ) ( struct page * page , unsigned long offset ,
Btrfs: Add zlib compression support
This is a large change for adding compression on reading and writing,
both for inline and regular extents. It does some fairly large
surgery to the writeback paths.
Compression is off by default and enabled by mount -o compress. Even
when the -o compress mount option is not used, it is possible to read
compressed extents off the disk.
If compression for a given set of pages fails to make them smaller, the
file is flagged to avoid future compression attempts later.
* While finding delalloc extents, the pages are locked before being sent down
to the delalloc handler. This allows the delalloc handler to do complex things
such as cleaning the pages, marking them writeback and starting IO on their
behalf.
* Inline extents are inserted at delalloc time now. This allows us to compress
the data before inserting the inline extent, and it allows us to insert
an inline extent that spans multiple pages.
* All of the in-memory extent representations (extent_map.c, ordered-data.c etc)
are changed to record both an in-memory size and an on disk size, as well
as a flag for compression.
From a disk format point of view, the extent pointers in the file are changed
to record the on disk size of a given extent and some encoding flags.
Space in the disk format is allocated for compression encoding, as well
as encryption and a generic 'other' field. Neither the encryption or the
'other' field are currently used.
In order to limit the amount of data read for a single random read in the
file, the size of a compressed extent is limited to 128k. This is a
software only limit, the disk format supports u64 sized compressed extents.
In order to limit the ram consumed while processing extents, the uncompressed
size of a compressed extent is limited to 256k. This is a software only limit
and will be subject to tuning later.
Checksumming is still done on compressed extents, and it is done on the
uncompressed version of the data. This way additional encodings can be
layered on without having to figure out which encoding to checksum.
Compression happens at delalloc time, which is basically singled threaded because
it is usually done by a single pdflush thread. This makes it tricky to
spread the compression load across all the cpus on the box. We'll have to
look at parallel pdflush walks of dirty inodes at a later time.
Decompression is hooked into readpages and it does spread across CPUs nicely.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2008-10-29 21:49:59 +03:00
size_t size , struct bio * bio ,
unsigned long bio_flags ) ;
2012-03-27 05:57:36 +04:00
int ( * readpage_io_failed_hook ) ( struct page * page , int failed_mirror ) ;
2013-07-25 15:22:34 +04:00
int ( * readpage_end_io_hook ) ( struct btrfs_io_bio * io_bio , u64 phy_offset ,
struct page * page , u64 start , u64 end ,
int mirror ) ;
2008-05-12 21:39:03 +04:00
int ( * writepage_end_io_hook ) ( struct page * page , u64 start , u64 end ,
2008-07-17 20:53:50 +04:00
struct extent_state * state , int uptodate ) ;
2011-07-21 20:56:09 +04:00
void ( * set_bit_hook ) ( struct inode * inode , struct extent_state * state ,
2015-01-14 21:52:13 +03:00
unsigned * bits ) ;
2011-07-21 20:56:09 +04:00
void ( * clear_bit_hook ) ( struct inode * inode , struct extent_state * state ,
2015-01-14 21:52:13 +03:00
unsigned * bits ) ;
2011-07-21 20:56:09 +04:00
void ( * merge_extent_hook ) ( struct inode * inode ,
struct extent_state * new ,
struct extent_state * other ) ;
void ( * split_extent_hook ) ( struct inode * inode ,
struct extent_state * orig , u64 split ) ;
2008-01-25 00:13:08 +03:00
} ;
struct extent_io_tree {
struct rb_root state ;
struct address_space * mapping ;
u64 dirty_bytes ;
2012-03-13 17:38:00 +04:00
int track_uptodate ;
2008-01-29 17:59:12 +03:00
spinlock_t lock ;
2015-01-02 20:23:10 +03:00
const struct extent_io_ops * ops ;
2008-01-25 00:13:08 +03:00
} ;
struct extent_state {
u64 start ;
u64 end ; /* inclusive */
struct rb_node rb_node ;
2009-09-12 00:12:44 +04:00
/* ADD NEW ELEMENTS AFTER THIS */
2008-01-25 00:13:08 +03:00
wait_queue_head_t wq ;
atomic_t refs ;
2015-01-14 21:52:13 +03:00
unsigned state ;
2008-01-25 00:13:08 +03:00
2016-02-11 15:24:13 +03:00
struct io_failure_record * failrec ;
2008-01-25 00:13:08 +03:00
2013-04-22 20:12:31 +04:00
# ifdef CONFIG_BTRFS_DEBUG
2008-03-26 23:24:23 +03:00
struct list_head leak_list ;
2013-04-22 20:12:31 +04:00
# endif
2008-01-25 00:13:08 +03:00
} ;
2010-08-06 21:21:20 +04:00
# define INLINE_EXTENT_BUFFER_PAGES 16
mm, fs: get rid of PAGE_CACHE_* and page_cache_{get,release} macros
PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} macros were introduced *long* time
ago with promise that one day it will be possible to implement page
cache with bigger chunks than PAGE_SIZE.
This promise never materialized. And unlikely will.
We have many places where PAGE_CACHE_SIZE assumed to be equal to
PAGE_SIZE. And it's constant source of confusion on whether
PAGE_CACHE_* or PAGE_* constant should be used in a particular case,
especially on the border between fs and mm.
Global switching to PAGE_CACHE_SIZE != PAGE_SIZE would cause to much
breakage to be doable.
Let's stop pretending that pages in page cache are special. They are
not.
The changes are pretty straight-forward:
- <foo> << (PAGE_CACHE_SHIFT - PAGE_SHIFT) -> <foo>;
- <foo> >> (PAGE_CACHE_SHIFT - PAGE_SHIFT) -> <foo>;
- PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} -> PAGE_{SIZE,SHIFT,MASK,ALIGN};
- page_cache_get() -> get_page();
- page_cache_release() -> put_page();
This patch contains automated changes generated with coccinelle using
script below. For some reason, coccinelle doesn't patch header files.
I've called spatch for them manually.
The only adjustment after coccinelle is revert of changes to
PAGE_CAHCE_ALIGN definition: we are going to drop it later.
There are few places in the code where coccinelle didn't reach. I'll
fix them manually in a separate patch. Comments and documentation also
will be addressed with the separate patch.
virtual patch
@@
expression E;
@@
- E << (PAGE_CACHE_SHIFT - PAGE_SHIFT)
+ E
@@
expression E;
@@
- E >> (PAGE_CACHE_SHIFT - PAGE_SHIFT)
+ E
@@
@@
- PAGE_CACHE_SHIFT
+ PAGE_SHIFT
@@
@@
- PAGE_CACHE_SIZE
+ PAGE_SIZE
@@
@@
- PAGE_CACHE_MASK
+ PAGE_MASK
@@
expression E;
@@
- PAGE_CACHE_ALIGN(E)
+ PAGE_ALIGN(E)
@@
expression E;
@@
- page_cache_get(E)
+ get_page(E)
@@
expression E;
@@
- page_cache_release(E)
+ put_page(E)
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-04-01 15:29:47 +03:00
# define MAX_INLINE_EXTENT_BUFFER_SIZE (INLINE_EXTENT_BUFFER_PAGES * PAGE_SIZE)
2008-01-25 00:13:08 +03:00
struct extent_buffer {
u64 start ;
unsigned long len ;
Btrfs: Change btree locking to use explicit blocking points
Most of the btrfs metadata operations can be protected by a spinlock,
but some operations still need to schedule.
So far, btrfs has been using a mutex along with a trylock loop,
most of the time it is able to avoid going for the full mutex, so
the trylock loop is a big performance gain.
This commit is step one for getting rid of the blocking locks entirely.
btrfs_tree_lock takes a spinlock, and the code explicitly switches
to a blocking lock when it starts an operation that can schedule.
We'll be able get rid of the blocking locks in smaller pieces over time.
Tracing allows us to find the most common cause of blocking, so we
can start with the hot spots first.
The basic idea is:
btrfs_tree_lock() returns with the spin lock held
btrfs_set_lock_blocking() sets the EXTENT_BUFFER_BLOCKING bit in
the extent buffer flags, and then drops the spin lock. The buffer is
still considered locked by all of the btrfs code.
If btrfs_tree_lock gets the spinlock but finds the blocking bit set, it drops
the spin lock and waits on a wait queue for the blocking bit to go away.
Much of the code that needs to set the blocking bit finishes without actually
blocking a good percentage of the time. So, an adaptive spin is still
used against the blocking bit to avoid very high context switch rates.
btrfs_clear_lock_blocking() clears the blocking bit and returns
with the spinlock held again.
btrfs_tree_unlock() can be called on either blocking or spinning locks,
it does the right thing based on the blocking bit.
ctree.c has a helper function to set/clear all the locked buffers in a
path as blocking.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-02-04 17:25:08 +03:00
unsigned long bflags ;
2013-12-16 22:24:27 +04:00
struct btrfs_fs_info * fs_info ;
2012-03-10 01:01:49 +04:00
spinlock_t refs_lock ;
2010-08-06 21:21:20 +04:00
atomic_t refs ;
2012-03-13 17:38:00 +04:00
atomic_t io_pages ;
2012-04-16 17:42:26 +04:00
int read_mirror ;
2010-10-27 04:57:29 +04:00
struct rcu_head rcu_head ;
2011-09-13 12:55:48 +04:00
pid_t lock_owner ;
Btrfs: Change btree locking to use explicit blocking points
Most of the btrfs metadata operations can be protected by a spinlock,
but some operations still need to schedule.
So far, btrfs has been using a mutex along with a trylock loop,
most of the time it is able to avoid going for the full mutex, so
the trylock loop is a big performance gain.
This commit is step one for getting rid of the blocking locks entirely.
btrfs_tree_lock takes a spinlock, and the code explicitly switches
to a blocking lock when it starts an operation that can schedule.
We'll be able get rid of the blocking locks in smaller pieces over time.
Tracing allows us to find the most common cause of blocking, so we
can start with the hot spots first.
The basic idea is:
btrfs_tree_lock() returns with the spin lock held
btrfs_set_lock_blocking() sets the EXTENT_BUFFER_BLOCKING bit in
the extent buffer flags, and then drops the spin lock. The buffer is
still considered locked by all of the btrfs code.
If btrfs_tree_lock gets the spinlock but finds the blocking bit set, it drops
the spin lock and waits on a wait queue for the blocking bit to go away.
Much of the code that needs to set the blocking bit finishes without actually
blocking a good percentage of the time. So, an adaptive spin is still
used against the blocking bit to avoid very high context switch rates.
btrfs_clear_lock_blocking() clears the blocking bit and returns
with the spinlock held again.
btrfs_tree_unlock() can be called on either blocking or spinning locks,
it does the right thing based on the blocking bit.
ctree.c has a helper function to set/clear all the locked buffers in a
path as blocking.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-02-04 17:25:08 +03:00
2011-07-16 23:23:14 +04:00
/* count of read lock holders on the extent buffer */
atomic_t write_locks ;
atomic_t read_locks ;
atomic_t blocking_writers ;
atomic_t blocking_readers ;
atomic_t spinning_readers ;
atomic_t spinning_writers ;
Btrfs: be aware of btree inode write errors to avoid fs corruption
While we have a transaction ongoing, the VM might decide at any time
to call btree_inode->i_mapping->a_ops->writepages(), which will start
writeback of dirty pages belonging to btree nodes/leafs. This call
might return an error or the writeback might finish with an error
before we attempt to commit the running transaction. If this happens,
we might have no way of knowing that such error happened when we are
committing the transaction - because the pages might no longer be
marked dirty nor tagged for writeback (if a subsequent modification
to the extent buffer didn't happen before the transaction commit) which
makes filemap_fdata[write|wait]_range unable to find such pages (even
if they're marked with SetPageError).
So if this happens we must abort the transaction, otherwise we commit
a super block with btree roots that point to btree nodes/leafs whose
content on disk is invalid - either garbage or the content of some
node/leaf from a past generation that got cowed or deleted and is no
longer valid (for this later case we end up getting error messages like
"parent transid verify failed on 10826481664 wanted 25748 found 29562"
when reading btree nodes/leafs from disk).
Note that setting and checking AS_EIO/AS_ENOSPC in the btree inode's
i_mapping would not be enough because we need to distinguish between
log tree extents (not fatal) vs non-log tree extents (fatal) and
because the next call to filemap_fdatawait_range() will catch and clear
such errors in the mapping - and that call might be from a log sync and
not from a transaction commit, which means we would not know about the
error at transaction commit time. Also, checking for the eb flag
EXTENT_BUFFER_IOERR at transaction commit time isn't done and would
not be completely reliable, as the eb might be removed from memory and
read back when trying to get it, which clears that flag right before
reading the eb's pages from disk, making us not know about the previous
write error.
Using the new 3 flags for the btree inode also makes us achieve the
goal of AS_EIO/AS_ENOSPC when writepages() returns success, started
writeback for all dirty pages and before filemap_fdatawait_range() is
called, the writeback for all dirty pages had already finished with
errors - because we were not using AS_EIO/AS_ENOSPC,
filemap_fdatawait_range() would return success, as it could not know
that writeback errors happened (the pages were no longer tagged for
writeback).
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Chris Mason <clm@fb.com>
2014-09-26 15:25:56 +04:00
short lock_nested ;
/* >= 0 if eb belongs to a log tree, -1 otherwise */
short log_index ;
2011-07-16 23:23:14 +04:00
/* protects write locks */
rwlock_t lock ;
/* readers use lock_wq while they wait for the write
* lock holders to unlock
*/
wait_queue_head_t write_lock_wq ;
Btrfs: Change btree locking to use explicit blocking points
Most of the btrfs metadata operations can be protected by a spinlock,
but some operations still need to schedule.
So far, btrfs has been using a mutex along with a trylock loop,
most of the time it is able to avoid going for the full mutex, so
the trylock loop is a big performance gain.
This commit is step one for getting rid of the blocking locks entirely.
btrfs_tree_lock takes a spinlock, and the code explicitly switches
to a blocking lock when it starts an operation that can schedule.
We'll be able get rid of the blocking locks in smaller pieces over time.
Tracing allows us to find the most common cause of blocking, so we
can start with the hot spots first.
The basic idea is:
btrfs_tree_lock() returns with the spin lock held
btrfs_set_lock_blocking() sets the EXTENT_BUFFER_BLOCKING bit in
the extent buffer flags, and then drops the spin lock. The buffer is
still considered locked by all of the btrfs code.
If btrfs_tree_lock gets the spinlock but finds the blocking bit set, it drops
the spin lock and waits on a wait queue for the blocking bit to go away.
Much of the code that needs to set the blocking bit finishes without actually
blocking a good percentage of the time. So, an adaptive spin is still
used against the blocking bit to avoid very high context switch rates.
btrfs_clear_lock_blocking() clears the blocking bit and returns
with the spinlock held again.
btrfs_tree_unlock() can be called on either blocking or spinning locks,
it does the right thing based on the blocking bit.
ctree.c has a helper function to set/clear all the locked buffers in a
path as blocking.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-02-04 17:25:08 +03:00
2011-07-16 23:23:14 +04:00
/* writers use read_lock_wq while they wait for readers
* to unlock
Btrfs: Change btree locking to use explicit blocking points
Most of the btrfs metadata operations can be protected by a spinlock,
but some operations still need to schedule.
So far, btrfs has been using a mutex along with a trylock loop,
most of the time it is able to avoid going for the full mutex, so
the trylock loop is a big performance gain.
This commit is step one for getting rid of the blocking locks entirely.
btrfs_tree_lock takes a spinlock, and the code explicitly switches
to a blocking lock when it starts an operation that can schedule.
We'll be able get rid of the blocking locks in smaller pieces over time.
Tracing allows us to find the most common cause of blocking, so we
can start with the hot spots first.
The basic idea is:
btrfs_tree_lock() returns with the spin lock held
btrfs_set_lock_blocking() sets the EXTENT_BUFFER_BLOCKING bit in
the extent buffer flags, and then drops the spin lock. The buffer is
still considered locked by all of the btrfs code.
If btrfs_tree_lock gets the spinlock but finds the blocking bit set, it drops
the spin lock and waits on a wait queue for the blocking bit to go away.
Much of the code that needs to set the blocking bit finishes without actually
blocking a good percentage of the time. So, an adaptive spin is still
used against the blocking bit to avoid very high context switch rates.
btrfs_clear_lock_blocking() clears the blocking bit and returns
with the spinlock held again.
btrfs_tree_unlock() can be called on either blocking or spinning locks,
it does the right thing based on the blocking bit.
ctree.c has a helper function to set/clear all the locked buffers in a
path as blocking.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-02-04 17:25:08 +03:00
*/
2011-07-16 23:23:14 +04:00
wait_queue_head_t read_lock_wq ;
2013-02-28 18:54:18 +04:00
struct page * pages [ INLINE_EXTENT_BUFFER_PAGES ] ;
2013-04-22 20:12:31 +04:00
# ifdef CONFIG_BTRFS_DEBUG
struct list_head leak_list ;
# endif
2008-01-25 00:13:08 +03:00
} ;
2015-10-12 07:08:16 +03:00
/*
* Structure to record how many bytes and which ranges are set / cleared
*/
struct extent_changeset {
/* How many bytes are set/cleared in this operation */
u64 bytes_changed ;
/* Changed ranges */
2017-02-13 15:42:29 +03:00
struct ulist range_changed ;
2015-10-12 07:08:16 +03:00
} ;
2010-12-17 09:21:50 +03:00
static inline void extent_set_compress_type ( unsigned long * bio_flags ,
int compress_type )
{
* bio_flags | = compress_type < < EXTENT_BIO_FLAG_SHIFT ;
}
static inline int extent_compress_type ( unsigned long bio_flags )
{
return bio_flags > > EXTENT_BIO_FLAG_SHIFT ;
}
2008-01-25 00:13:08 +03:00
struct extent_map_tree ;
typedef struct extent_map * ( get_extent_t ) ( struct inode * inode ,
struct page * page ,
2011-04-19 16:29:38 +04:00
size_t pg_offset ,
2008-01-25 00:13:08 +03:00
u64 start , u64 len ,
int create ) ;
void extent_io_tree_init ( struct extent_io_tree * tree ,
2011-04-21 01:35:57 +04:00
struct address_space * mapping ) ;
2008-01-25 00:13:08 +03:00
int try_release_extent_mapping ( struct extent_map_tree * map ,
2008-01-29 17:59:12 +03:00
struct extent_io_tree * tree , struct page * page ,
gfp_t mask ) ;
2013-04-26 18:56:29 +04:00
int try_release_extent_buffer ( struct page * page ) ;
2009-09-02 21:24:36 +04:00
int lock_extent_bits ( struct extent_io_tree * tree , u64 start , u64 end ,
2015-12-03 16:30:40 +03:00
struct extent_state * * cached ) ;
2015-12-03 16:41:30 +03:00
static inline int lock_extent ( struct extent_io_tree * tree , u64 start , u64 end )
{
return lock_extent_bits ( tree , start , end , NULL ) ;
}
2012-03-01 17:57:19 +04:00
int try_lock_extent ( struct extent_io_tree * tree , u64 start , u64 end ) ;
2008-01-25 00:13:08 +03:00
int extent_read_full_page ( struct extent_io_tree * tree , struct page * page ,
2011-06-13 22:02:58 +04:00
get_extent_t * get_extent , int mirror_num ) ;
2008-01-25 00:13:08 +03:00
int __init extent_io_init ( void ) ;
void extent_io_exit ( void ) ;
u64 count_range_bits ( struct extent_io_tree * tree ,
u64 * start , u64 search_end ,
2015-01-14 21:52:13 +03:00
u64 max_bytes , unsigned bits , int contig ) ;
2008-01-25 00:13:08 +03:00
2010-05-26 04:56:50 +04:00
void free_extent_state ( struct extent_state * state ) ;
2008-01-25 00:13:08 +03:00
int test_range_bit ( struct extent_io_tree * tree , u64 start , u64 end ,
2015-01-14 21:52:13 +03:00
unsigned bits , int filled ,
2013-04-29 17:38:46 +04:00
struct extent_state * cached_state ) ;
2015-10-12 10:35:38 +03:00
int clear_record_extent_bits ( struct extent_io_tree * tree , u64 start , u64 end ,
2016-04-27 00:54:39 +03:00
unsigned bits , struct extent_changeset * changeset ) ;
2008-07-17 20:53:50 +04:00
int clear_extent_bit ( struct extent_io_tree * tree , u64 start , u64 end ,
2015-01-14 21:52:13 +03:00
unsigned bits , int wake , int delete ,
2013-04-29 17:38:46 +04:00
struct extent_state * * cached , gfp_t mask ) ;
2015-12-03 16:08:11 +03:00
2015-12-03 16:08:11 +03:00
static inline int unlock_extent ( struct extent_io_tree * tree , u64 start , u64 end )
{
return clear_extent_bit ( tree , start , end , EXTENT_LOCKED , 1 , 0 , NULL ,
GFP_NOFS ) ;
}
static inline int unlock_extent_cached ( struct extent_io_tree * tree , u64 start ,
u64 end , struct extent_state * * cached , gfp_t mask )
{
return clear_extent_bit ( tree , start , end , EXTENT_LOCKED , 1 , 0 , cached ,
mask ) ;
}
static inline int clear_extent_bits ( struct extent_io_tree * tree , u64 start ,
2016-04-27 00:54:39 +03:00
u64 end , unsigned bits )
2015-12-03 16:08:11 +03:00
{
int wake = 0 ;
if ( bits & EXTENT_LOCKED )
wake = 1 ;
2016-04-27 00:54:39 +03:00
return clear_extent_bit ( tree , start , end , bits , wake , 0 , NULL ,
GFP_NOFS ) ;
2015-12-03 16:08:11 +03:00
}
2015-10-12 09:53:37 +03:00
int set_record_extent_bits ( struct extent_io_tree * tree , u64 start , u64 end ,
2016-04-27 00:54:39 +03:00
unsigned bits , struct extent_changeset * changeset ) ;
2010-05-26 04:56:50 +04:00
int set_extent_bit ( struct extent_io_tree * tree , u64 start , u64 end ,
2015-01-14 21:52:13 +03:00
unsigned bits , u64 * failed_start ,
2010-05-26 04:56:50 +04:00
struct extent_state * * cached_state , gfp_t mask ) ;
2015-12-03 16:08:11 +03:00
static inline int set_extent_bits ( struct extent_io_tree * tree , u64 start ,
2016-04-27 00:54:39 +03:00
u64 end , unsigned bits )
2015-12-03 16:08:11 +03:00
{
2016-04-27 00:54:39 +03:00
return set_extent_bit ( tree , start , end , bits , NULL , NULL , GFP_NOFS ) ;
2015-12-03 16:08:11 +03:00
}
2015-12-03 16:08:11 +03:00
static inline int clear_extent_uptodate ( struct extent_io_tree * tree , u64 start ,
u64 end , struct extent_state * * cached_state , gfp_t mask )
{
return clear_extent_bit ( tree , start , end , EXTENT_UPTODATE , 0 , 0 ,
cached_state , mask ) ;
}
2015-12-03 16:08:11 +03:00
static inline int set_extent_dirty ( struct extent_io_tree * tree , u64 start ,
u64 end , gfp_t mask )
{
return set_extent_bit ( tree , start , end , EXTENT_DIRTY , NULL ,
NULL , mask ) ;
}
2015-12-03 16:08:11 +03:00
static inline int clear_extent_dirty ( struct extent_io_tree * tree , u64 start ,
2016-04-27 00:54:39 +03:00
u64 end )
2015-12-03 16:08:11 +03:00
{
return clear_extent_bit ( tree , start , end ,
EXTENT_DIRTY | EXTENT_DELALLOC |
2016-04-27 00:54:39 +03:00
EXTENT_DO_ACCOUNTING , 0 , 0 , NULL , GFP_NOFS ) ;
2015-12-03 16:08:11 +03:00
}
2011-09-26 21:56:12 +04:00
int convert_extent_bit ( struct extent_io_tree * tree , u64 start , u64 end ,
2015-01-14 21:52:13 +03:00
unsigned bits , unsigned clear_bits ,
2016-04-27 00:54:39 +03:00
struct extent_state * * cached_state ) ;
2015-12-03 16:08:11 +03:00
static inline int set_extent_delalloc ( struct extent_io_tree * tree , u64 start ,
2016-04-27 00:54:39 +03:00
u64 end , struct extent_state * * cached_state )
2015-12-03 16:08:11 +03:00
{
return set_extent_bit ( tree , start , end ,
EXTENT_DELALLOC | EXTENT_UPTODATE ,
2016-04-27 00:54:39 +03:00
NULL , cached_state , GFP_NOFS ) ;
2015-12-03 16:08:11 +03:00
}
static inline int set_extent_defrag ( struct extent_io_tree * tree , u64 start ,
2016-04-27 00:54:39 +03:00
u64 end , struct extent_state * * cached_state )
2015-12-03 16:08:11 +03:00
{
return set_extent_bit ( tree , start , end ,
EXTENT_DELALLOC | EXTENT_UPTODATE | EXTENT_DEFRAG ,
2016-04-27 00:54:39 +03:00
NULL , cached_state , GFP_NOFS ) ;
2015-12-03 16:08:11 +03:00
}
static inline int set_extent_new ( struct extent_io_tree * tree , u64 start ,
2016-04-27 00:54:39 +03:00
u64 end )
2015-12-03 16:08:11 +03:00
{
2016-04-27 00:54:39 +03:00
return set_extent_bit ( tree , start , end , EXTENT_NEW , NULL , NULL ,
GFP_NOFS ) ;
2015-12-03 16:08:11 +03:00
}
static inline int set_extent_uptodate ( struct extent_io_tree * tree , u64 start ,
u64 end , struct extent_state * * cached_state , gfp_t mask )
{
return set_extent_bit ( tree , start , end , EXTENT_UPTODATE , NULL ,
cached_state , mask ) ;
}
2008-01-25 00:13:08 +03:00
int find_first_extent_bit ( struct extent_io_tree * tree , u64 start ,
2015-01-14 21:52:13 +03:00
u64 * start_ret , u64 * end_ret , unsigned bits ,
2012-09-28 01:07:30 +04:00
struct extent_state * * cached_state ) ;
2008-01-25 00:13:08 +03:00
int extent_invalidatepage ( struct extent_io_tree * tree ,
struct page * page , unsigned long offset ) ;
int extent_write_full_page ( struct extent_io_tree * tree , struct page * page ,
get_extent_t * get_extent ,
struct writeback_control * wbc ) ;
2008-11-07 06:02:51 +03:00
int extent_write_locked_range ( struct extent_io_tree * tree , struct inode * inode ,
u64 start , u64 end , get_extent_t * get_extent ,
int mode ) ;
2008-01-25 00:13:08 +03:00
int extent_writepages ( struct extent_io_tree * tree ,
struct address_space * mapping ,
get_extent_t * get_extent ,
struct writeback_control * wbc ) ;
2012-03-13 17:38:00 +04:00
int btree_write_cache_pages ( struct address_space * mapping ,
struct writeback_control * wbc ) ;
2008-01-25 00:13:08 +03:00
int extent_readpages ( struct extent_io_tree * tree ,
struct address_space * mapping ,
struct list_head * pages , unsigned nr_pages ,
get_extent_t get_extent ) ;
2009-01-21 22:39:14 +03:00
int extent_fiemap ( struct inode * inode , struct fiemap_extent_info * fieinfo ,
__u64 start , __u64 len , get_extent_t * get_extent ) ;
2008-01-25 00:13:08 +03:00
void set_page_extent_mapped ( struct page * page ) ;
2013-12-16 22:24:27 +04:00
struct extent_buffer * alloc_extent_buffer ( struct btrfs_fs_info * fs_info ,
2014-06-15 05:00:04 +04:00
u64 start ) ;
2015-09-30 06:50:31 +03:00
struct extent_buffer * __alloc_dummy_extent_buffer ( struct btrfs_fs_info * fs_info ,
u64 start , unsigned long len ) ;
2014-06-15 05:20:26 +04:00
struct extent_buffer * alloc_dummy_extent_buffer ( struct btrfs_fs_info * fs_info ,
2016-06-15 16:22:56 +03:00
u64 start ) ;
2012-05-16 19:00:02 +04:00
struct extent_buffer * btrfs_clone_extent_buffer ( struct extent_buffer * src ) ;
2013-12-16 22:24:27 +04:00
struct extent_buffer * find_extent_buffer ( struct btrfs_fs_info * fs_info ,
2013-10-07 19:45:25 +04:00
u64 start ) ;
2008-01-25 00:13:08 +03:00
void free_extent_buffer ( struct extent_buffer * eb ) ;
2012-03-10 01:01:49 +04:00
void free_extent_buffer_stale ( struct extent_buffer * eb ) ;
2011-06-10 16:06:53 +04:00
# define WAIT_NONE 0
# define WAIT_COMPLETE 1
# define WAIT_PAGE_LOCK 2
2008-01-25 00:13:08 +03:00
int read_extent_buffer_pages ( struct extent_io_tree * tree ,
2016-09-02 22:40:03 +03:00
struct extent_buffer * eb , int wait ,
2008-04-10 00:28:12 +04:00
get_extent_t * get_extent , int mirror_num ) ;
2013-04-25 00:41:19 +04:00
void wait_on_extent_buffer_writeback ( struct extent_buffer * eb ) ;
2012-09-29 12:07:47 +04:00
static inline unsigned long num_extent_pages ( u64 start , u64 len )
{
mm, fs: get rid of PAGE_CACHE_* and page_cache_{get,release} macros
PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} macros were introduced *long* time
ago with promise that one day it will be possible to implement page
cache with bigger chunks than PAGE_SIZE.
This promise never materialized. And unlikely will.
We have many places where PAGE_CACHE_SIZE assumed to be equal to
PAGE_SIZE. And it's constant source of confusion on whether
PAGE_CACHE_* or PAGE_* constant should be used in a particular case,
especially on the border between fs and mm.
Global switching to PAGE_CACHE_SIZE != PAGE_SIZE would cause to much
breakage to be doable.
Let's stop pretending that pages in page cache are special. They are
not.
The changes are pretty straight-forward:
- <foo> << (PAGE_CACHE_SHIFT - PAGE_SHIFT) -> <foo>;
- <foo> >> (PAGE_CACHE_SHIFT - PAGE_SHIFT) -> <foo>;
- PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} -> PAGE_{SIZE,SHIFT,MASK,ALIGN};
- page_cache_get() -> get_page();
- page_cache_release() -> put_page();
This patch contains automated changes generated with coccinelle using
script below. For some reason, coccinelle doesn't patch header files.
I've called spatch for them manually.
The only adjustment after coccinelle is revert of changes to
PAGE_CAHCE_ALIGN definition: we are going to drop it later.
There are few places in the code where coccinelle didn't reach. I'll
fix them manually in a separate patch. Comments and documentation also
will be addressed with the separate patch.
virtual patch
@@
expression E;
@@
- E << (PAGE_CACHE_SHIFT - PAGE_SHIFT)
+ E
@@
expression E;
@@
- E >> (PAGE_CACHE_SHIFT - PAGE_SHIFT)
+ E
@@
@@
- PAGE_CACHE_SHIFT
+ PAGE_SHIFT
@@
@@
- PAGE_CACHE_SIZE
+ PAGE_SIZE
@@
@@
- PAGE_CACHE_MASK
+ PAGE_MASK
@@
expression E;
@@
- PAGE_CACHE_ALIGN(E)
+ PAGE_ALIGN(E)
@@
expression E;
@@
- page_cache_get(E)
+ get_page(E)
@@
expression E;
@@
- page_cache_release(E)
+ put_page(E)
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-04-01 15:29:47 +03:00
return ( ( start + len + PAGE_SIZE - 1 ) > > PAGE_SHIFT ) -
( start > > PAGE_SHIFT ) ;
2012-09-29 12:07:47 +04:00
}
2008-01-25 00:13:08 +03:00
static inline void extent_buffer_get ( struct extent_buffer * eb )
{
atomic_inc ( & eb - > refs ) ;
}
int memcmp_extent_buffer ( struct extent_buffer * eb , const void * ptrv ,
unsigned long start ,
unsigned long len ) ;
void read_extent_buffer ( struct extent_buffer * eb , void * dst ,
unsigned long start ,
unsigned long len ) ;
2014-01-30 19:24:01 +04:00
int read_extent_buffer_to_user ( struct extent_buffer * eb , void __user * dst ,
unsigned long start ,
unsigned long len ) ;
2016-11-09 19:43:38 +03:00
void write_extent_buffer_fsid ( struct extent_buffer * eb , const void * src ) ;
void write_extent_buffer_chunk_tree_uuid ( struct extent_buffer * eb ,
const void * src ) ;
2008-01-25 00:13:08 +03:00
void write_extent_buffer ( struct extent_buffer * eb , const void * src ,
unsigned long start , unsigned long len ) ;
2016-11-08 20:30:31 +03:00
void copy_extent_buffer_full ( struct extent_buffer * dst ,
struct extent_buffer * src ) ;
2008-01-25 00:13:08 +03:00
void copy_extent_buffer ( struct extent_buffer * dst , struct extent_buffer * src ,
unsigned long dst_offset , unsigned long src_offset ,
unsigned long len ) ;
void memcpy_extent_buffer ( struct extent_buffer * dst , unsigned long dst_offset ,
unsigned long src_offset , unsigned long len ) ;
void memmove_extent_buffer ( struct extent_buffer * dst , unsigned long dst_offset ,
unsigned long src_offset , unsigned long len ) ;
2016-11-08 20:09:03 +03:00
void memzero_extent_buffer ( struct extent_buffer * eb , unsigned long start ,
unsigned long len ) ;
2015-09-30 06:50:30 +03:00
int extent_buffer_test_bit ( struct extent_buffer * eb , unsigned long start ,
unsigned long pos ) ;
void extent_buffer_bitmap_set ( struct extent_buffer * eb , unsigned long start ,
unsigned long pos , unsigned long len ) ;
void extent_buffer_bitmap_clear ( struct extent_buffer * eb , unsigned long start ,
unsigned long pos , unsigned long len ) ;
2012-03-29 04:31:37 +04:00
void clear_extent_buffer_dirty ( struct extent_buffer * eb ) ;
2012-03-13 17:38:00 +04:00
int set_extent_buffer_dirty ( struct extent_buffer * eb ) ;
2015-12-03 15:08:59 +03:00
void set_extent_buffer_uptodate ( struct extent_buffer * eb ) ;
2015-12-03 15:08:59 +03:00
void clear_extent_buffer_uptodate ( struct extent_buffer * eb ) ;
2012-03-13 17:38:00 +04:00
int extent_buffer_uptodate ( struct extent_buffer * eb ) ;
2014-03-29 01:07:27 +04:00
int extent_buffer_under_io ( struct extent_buffer * eb ) ;
2008-01-25 00:13:08 +03:00
int map_private_extent_buffer ( struct extent_buffer * eb , unsigned long offset ,
2011-07-19 20:04:14 +04:00
unsigned long min_len , char * * map ,
2008-01-25 00:13:08 +03:00
unsigned long * map_start ,
2011-07-19 20:04:14 +04:00
unsigned long * map_len ) ;
2015-12-03 15:08:59 +03:00
void extent_range_clear_dirty_for_io ( struct inode * inode , u64 start , u64 end ) ;
2015-12-03 15:08:59 +03:00
void extent_range_redirty_for_io ( struct inode * inode , u64 start , u64 end ) ;
2015-12-03 15:08:59 +03:00
void extent_clear_unlock_delalloc ( struct inode * inode , u64 start , u64 end ,
2016-07-19 11:50:36 +03:00
u64 delalloc_end , struct page * locked_page ,
2015-01-14 21:52:13 +03:00
unsigned bits_to_clear ,
2013-07-29 19:20:47 +04:00
unsigned long page_ops ) ;
2010-11-22 06:02:55 +03:00
struct bio *
btrfs_bio_alloc ( struct block_device * bdev , u64 first_sector , int nr_vecs ,
gfp_t gfp_flags ) ;
2013-05-18 02:30:14 +04:00
struct bio * btrfs_io_bio_alloc ( gfp_t gfp_mask , unsigned int nr_iovecs ) ;
struct bio * btrfs_bio_clone ( struct bio * bio , gfp_t gfp_mask ) ;
2011-07-22 17:41:52 +04:00
2012-11-05 18:46:42 +04:00
struct btrfs_fs_info ;
2011-07-22 17:41:52 +04:00
2014-09-12 14:44:01 +04:00
int repair_io_failure ( struct inode * inode , u64 start , u64 length , u64 logical ,
struct page * page , unsigned int pg_offset ,
int mirror_num ) ;
2014-09-12 14:44:03 +04:00
int clean_io_failure ( struct inode * inode , u64 start , struct page * page ,
unsigned int pg_offset ) ;
2015-12-03 15:08:59 +03:00
void end_extent_writepage ( struct page * page , int err , u64 start , u64 end ) ;
2016-06-23 01:54:24 +03:00
int repair_eb_io_failure ( struct btrfs_fs_info * fs_info ,
struct extent_buffer * eb , int mirror_num ) ;
2014-09-12 14:43:59 +04:00
/*
* When IO fails , either with EIO or csum verification fails , we
* try other mirrors that might have a good copy of the data . This
* io_failure_record is used to record state as we go through all the
* mirrors . If another mirror has good data , the page is set up to date
* and things continue . If a good mirror can ' t be found , the original
* bio end_io callback is called to indicate things have failed .
*/
struct io_failure_record {
struct page * page ;
u64 start ;
u64 len ;
u64 logical ;
unsigned long bio_flags ;
int this_mirror ;
int failed_mirror ;
int in_validation ;
} ;
2017-02-20 14:50:52 +03:00
struct btrfs_inode ;
Btrfs: cleanup the read failure record after write or when the inode is freeing
After the data is written successfully, we should cleanup the read failure record
in that range because
- If we set data COW for the file, the range that the failure record pointed to is
mapped to a new place, so it is invalid.
- If we set no data COW for the file, and if there is no error during writting,
the corrupted data is corrected, so the failure record can be removed. And if
some errors happen on the mirrors, we also needn't worry about it because the
failure record will be recreated if we read the same place again.
Sometimes, we may fail to correct the data, so the failure records will be left
in the tree, we need free them when we free the inode or the memory leak happens.
Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Chris Mason <clm@fb.com>
2014-09-12 14:44:04 +04:00
void btrfs_free_io_failure_record ( struct inode * inode , u64 start , u64 end ) ;
2014-09-12 14:43:59 +04:00
int btrfs_get_io_failure_record ( struct inode * inode , u64 start , u64 end ,
struct io_failure_record * * failrec_ret ) ;
int btrfs_check_repairable ( struct inode * inode , struct bio * failed_bio ,
struct io_failure_record * failrec , int fail_mirror ) ;
struct bio * btrfs_create_repair_bio ( struct inode * inode , struct bio * failed_bio ,
struct io_failure_record * failrec ,
struct page * page , int pg_offset , int icsum ,
2014-09-12 14:44:03 +04:00
bio_end_io_t * endio_func , void * data ) ;
2017-02-20 14:50:52 +03:00
int free_io_failure ( struct btrfs_inode * inode , struct io_failure_record * rec ) ;
2013-10-09 20:00:56 +04:00
# ifdef CONFIG_BTRFS_FS_RUN_SANITY_TESTS
noinline u64 find_lock_delalloc_range ( struct inode * inode ,
struct extent_io_tree * tree ,
struct page * locked_page , u64 * start ,
u64 * end , u64 max_bytes ) ;
2014-10-08 00:24:20 +04:00
# endif
2014-05-08 01:06:09 +04:00
struct extent_buffer * alloc_test_extent_buffer ( struct btrfs_fs_info * fs_info ,
2016-06-15 16:22:56 +03:00
u64 start ) ;
2013-10-09 20:00:56 +04:00
# endif
