diff options
| author |   Dmitry Monakhov <dmonakhov@openvz.org> | 2014-08-30 23:52:19 -0400 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2014-08-30 23:52:19 -0400 |
| commit | fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a (patch) | |
| tree | 008646f85f1b0b5cb2307c3c676eee431ac4ac29 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | ext4: use ext4_ext_next_allocated_block instead of mext_next_extent (diff) | |
| download | wireguard-linux-fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a.tar.xz wireguard-linux-fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a.zip | |
ext4: refactor ext4_move_extents code base
ext4_move_extents is too complex for review. It has duplicate almost
each function available in the rest of other codebase. It has useless
artificial restriction orig_offset == donor_offset. But in fact logic
of ext4_move_extents is very simple:
Iterate extents one by one (similar to ext4_fill_fiemap_extents)
->Iterate each page covered extent (similar to generic_perform_write)
->swap extents for covered by page (can be shared with IOC_MOVE_DATA)
Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions