Messages in this thread |  | | Subject | Re: [PATCH 2/2] xfs: fix stale data exposure problem when punch hole, collapse range or zero range across a delalloc extent | From | "yukuai (C)" <> | Date | Tue, 7 Jan 2020 10:09:44 +0800 |
| |
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
|  |