Ocfs2: Optimize ocfs2 truncating codes.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Ocfs2-devel] [PATCH 0/3] Ocfs2: Optimize ocfs2 truncating codes.
Hi all,
Optimization for ocfs2 truncating including following three patches, our main goal is to generalize truncating codes by using
common ocfs2_remove_btree_range() together with punching holes codes, besides, refcount supporting codes will be transfered from ocfs2_commit_truncate() to ocfs2_remove_btree_range() to let it be more generic, which will also benefit our punching holes codes
as well.
Such patches has been tested slightly(with normal and corner testcases), heavier workload are going to be expected.
We're going to optimize the punching holes codes in next series, on one hand, to truncate records as truncting codes did(from hole_end to hole_start),
on the other hand, add refcount supporting for it.
Regards,
Tristan.