Home
last modified time | relevance | path

Searched hist:"3 c6c2bebef79999b1827041696dc1881e637e3af" (Results 1 – 4 of 4) sorted by relevance

/openbmc/linux/fs/f2fs/
H A Dinode.cdiff 3c6c2bebef79999b1827041696dc1881e637e3af Tue Mar 17 19:16:35 CDT 2015 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: avoid punch_hole overhead when releasing volatile data

This patch is to avoid some punch_hole overhead when releasing volatile data.
If volatile data was not written yet, we just can make the first page as zero.

Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
H A Ddata.cdiff 3c6c2bebef79999b1827041696dc1881e637e3af Tue Mar 17 19:16:35 CDT 2015 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: avoid punch_hole overhead when releasing volatile data

This patch is to avoid some punch_hole overhead when releasing volatile data.
If volatile data was not written yet, we just can make the first page as zero.

Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
H A Dfile.cdiff 3c6c2bebef79999b1827041696dc1881e637e3af Tue Mar 17 19:16:35 CDT 2015 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: avoid punch_hole overhead when releasing volatile data

This patch is to avoid some punch_hole overhead when releasing volatile data.
If volatile data was not written yet, we just can make the first page as zero.

Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
H A Df2fs.hdiff 3c6c2bebef79999b1827041696dc1881e637e3af Tue Mar 17 19:16:35 CDT 2015 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: avoid punch_hole overhead when releasing volatile data

This patch is to avoid some punch_hole overhead when releasing volatile data.
If volatile data was not written yet, we just can make the first page as zero.

Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>