Date: Thu, 11 Feb 2016 00:35:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 206652] [ext2fs][patch] EXT4: sparse file fixes and mmap optimizations Message-ID: <bug-206652-3630-n1yLFULfY8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206652-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-206652-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206652 --- Comment #3 from commit-hook@freebsd.org --- A commit references this bug: Author: pfg Date: Thu Feb 11 00:34:12 UTC 2016 New revision: 295494 URL: https://svnweb.freebsd.org/changeset/base/295494 Log: Ext4: fix handling of files with sparse blocks before extent's index. This is ongoing work from Damjan Jovanovic to improve ext4 read support with sparse files: Keep track of the first and last block in each extent as it descends down the extent tree, thus being able to work out that some blocks are sparse earlier. This solves an issue on r293680. In ext4_bmapext() start supporting the runb parameter, which appears to be the number of adjacent blocks prior to the block being converted in the same way that runp is the number of blocks after, speding up random access to mmaped files. PR: 206652 Changes: head/sys/fs/ext2fs/ext2_bmap.c head/sys/fs/ext2fs/ext2_extents.c --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206652-3630-n1yLFULfY8>