Re: lz4 status?
On Thu, Aug 14, 2014 at 07:17:29AM -0600, Roger Pack wrote: Any update here re: lz4 integration? I noticed some people here saying they saw it not available yet? http://www.phoronix.com/forums/showthread.php?94912-Btrfs-Gets-Big-Changes-Features-In-Linux-3-14-Kernel https://btrfs.wiki.kernel.org/index.php/FAQ#Will_btrfs_support_LZ4.3F -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: lz4 status?
Quoting David Sterba (2013-07-10 18:54:54) On Sun, Jun 30, 2013 at 12:35:09PM -0500, Mitch Harder wrote: There's been a parallel effort to incorporate a general set of lz4 patches in the kernel. I see these patches are currently queued up in the linux-next tree, so we may see them in the 3.11 kernel. The patches are now merged into 3.11. It looks like lz4 and lz4hc will be provided. Regarding HC mode, there are some core compression code changes needed in order to fully utilize the its potential, namely larger chunk size that's compressed at a time. There was some tiny yet measurable gain of HC against ordinary mode compared on current 4k-at-a-time implementation, but the space savings did not justify the speed drop of HC mode. I can't say if the patchset will be ready for 3.12 though. The current limits on the amount of data compressed at a time and the amount of delayed allocation sent down at a time were pulled out of the air. Changes to those limits are definitely ok if they are helping specific workloads. -chris -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: lz4 status?
On Sun, Jun 30, 2013 at 12:35:09PM -0500, Mitch Harder wrote: There's been a parallel effort to incorporate a general set of lz4 patches in the kernel. I see these patches are currently queued up in the linux-next tree, so we may see them in the 3.11 kernel. The patches are now merged into 3.11. It looks like lz4 and lz4hc will be provided. Regarding HC mode, there are some core compression code changes needed in order to fully utilize the its potential, namely larger chunk size that's compressed at a time. There was some tiny yet measurable gain of HC against ordinary mode compared on current 4k-at-a-time implementation, but the space savings did not justify the speed drop of HC mode. I can't say if the patchset will be ready for 3.12 though. david -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: lz4 status?
On Sun, Jun 30, 2013 at 11:35 AM, Mitch Harder mitch.har...@sabayonlinux.org wrote: There's been a parallel effort to incorporate a general set of lz4 patches in the kernel. I see these patches are currently queued up in the linux-next tree, so we may see them in the 3.11 kernel. It looks like lz4 and lz4hc will be provided. So, instead of btrfs having it's own implementation of lz4, the patches will be re-worked around kernel's new lz4 library. Sounds good, keep up the good work :) roger -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: lz4 status?
There's been a parallel effort to incorporate a general set of lz4 patches in the kernel. I see these patches are currently queued up in the linux-next tree, so we may see them in the 3.11 kernel. It looks like lz4 and lz4hc will be provided. So, instead of btrfs having it's own implementation of lz4, the patches will be re-worked around kernel's new lz4 library. On Wed, Jun 26, 2013 at 10:57 AM, Roger Pack rogerpack2...@gmail.com wrote: Any update on the unmerged lz4 patches? Have they been merged? Just wondering (and +1'ing my support, obviously). Thank you. -roger- -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
