lkml.org 
[lkml]   [2020]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 2/2] xfs: fix stale data exposure problem when punch hole, collapse range or zero range across a delalloc extent
From
Date


On 2020/1/7 5:57, Darrick J. Wong wrote:
> So your solution is to split the delalloc reservation to constrain the
> allocation to the range that's being operated on?
Yes, I'm trying to split delalloc reservation.
>
> If so, I think a better solution (at least from the perspective of
> reducing fragmentation) would be to map the extent unwritten and force a
> post-writeback conversion[1] but I got shot down for performance reasons
> the last time I suggested that.
I'm wondering if spliting delalloc reservation have the same performance
issue.

Thanks!
Yu Kuai

\
 
 \ /
  Last update: 2020-01-07 03:10    [W:0.519 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site