Files
linux/fs
Josef Bacik 4f4db2174d Btrfs: keep track of max_extent_size per space_info
When we are heavily fragmented we can induce a lot of latency trying to make an
allocation happen that is simply not going to happen.  Thankfully we keep track
of our max_extent_size when going through the allocator, so if we get to the
point where we are exiting find_free_extent with ENOSPC then set our
space_info->max_extent_size so we can keep future allocations from having to pay
this cost.  We reset the max_extent_size whenever we release pinned bytes back
into this space info so we can redo all the work.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fb.com>
Signed-off-by: Chris Mason <clm@fb.com>
2015-10-21 18:55:19 -07:00
..
2015-06-30 19:44:57 -07:00
2015-06-23 18:02:01 -04:00
2015-10-03 16:54:17 -05:00
2015-06-25 17:00:42 -07:00
2015-09-08 15:35:28 -07:00
2015-08-16 12:35:44 -07:00
2015-08-13 12:32:04 -06:00
2015-08-13 12:32:04 -06:00
2015-04-11 22:29:40 -04:00
2015-09-08 15:35:28 -07:00
2014-11-19 13:01:20 -05:00
2015-07-09 11:42:21 -07:00
2015-08-13 12:32:04 -06:00
2015-07-23 20:59:40 +02:00
2015-08-12 15:28:45 -05:00
2015-08-31 16:27:25 -04:00
2015-09-04 16:54:41 -07:00
2015-08-13 12:32:04 -06:00
2014-08-26 09:35:56 +02:00