Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce ZSTD compression to ZFS #10278

Closed
wants to merge 5 commits into from

Commits on Aug 19, 2020

  1. Import ZStandard v1.4.5

    ZStandard is a modern, high performance, general compression algorithm.
    It provides similar or better compression levels to GZIP, but with much
    better performance. ZStandard provides a large selection of compression
    levels to allow a storage administrator to select the preferred
    performance/compression trade-off.
    
    This commit imports the unmodified ZStandard single-file library which
    will be used by ZFS.
    
    The implementation of this new library is done with future updates of
    zstd in mind. For this reason we integrated the code in a way, that does
    not require modifications to the library. For more details, see
    `module/zstd/README.md`.
    
    The library is excluded from codecov calculation and cppcheck as
    unaltered dependencies do not need full codecov or cppcheck.
    
    Co-authored-by: Allan Jude <[email protected]>
    Co-authored-by: Kjeld Schouten-Lebbing <[email protected]>
    Co-authored-by: Michael Niewöhner <[email protected]>
    Signed-off-by: Allan Jude <[email protected]>
    Signed-off-by: Kjeld Schouten-Lebbing <[email protected]>
    Signed-off-by: Michael Niewöhner <[email protected]>
    3 people committed Aug 19, 2020
    Configuration menu
    Copy the full SHA
    596a222 View commit details
    Browse the repository at this point in the history
  2. Add zstd support to zfs

    This PR adds two new compression types, based on ZStandard:
    
    - zstd: A basic ZStandard compression algorithm Available compression.
      Levels for zstd are zstd-1 through zstd-19, where the compression
      increases with every level, but speed decreases.
    
    - zstd-fast: A faster version of the ZStandard compression algorithm
      zstd-fast is basically a "negative" level of zstd. The compression
      decreases with every level, but speed increases.
    
      Available compression levels for zstd-fast:
       - zstd-fast-1 through zstd-fast-10
       - zstd-fast-20 through zstd-fast-100 (in increments of 10)
       - zstd-fast-500 and zstd-fast-1000
    
    For more information check the man page.
    
    Implementation details:
    
    Rather than treat each level of zstd as a different algorithm (as was
    done historically with gzip), the block pointer `enum zio_compress`
    value is simply zstd for all levels, including zstd-fast, since they all
    use the same decompression function.
    
    The compress= property (a 64bit unsigned integer) uses the lower 7 bits
    to store the compression algorithm (matching the number of bits used in
    a block pointer, as the 8th bit was borrowed for embedded block
    pointers).  The upper bits are used to store the compression level.
    
    It is necessary to be able to determine what compression level was used
    when later reading a block back, so the concept used in LZ4, where the
    first 32bits of the on-disk value are the size of the compressed data
    (since the allocation is rounded up to the nearest ashift), was
    extended, and we store the version of ZSTD and the level as well as the
    compressed size. This value is returned when decompressing a block, so
    that if the block needs to be recompressed (L2ARC, nop-write, etc), that
    the same parameters will be used to result in the matching checksum.
    
    All of the internal ZFS code ( `arc_buf_hdr_t`, `objset_t`,
    `zio_prop_t`, etc.) uses the separated _compress and _complevel
    variables.  Only the properties ZAP contains the combined/bit-shifted
    value. The combined value is split when the compression_changed_cb()
    callback is called, and sets both objset members (os_compress and
    os_complevel).
    
    The userspace tools all use the combined/bit-shifted value.
    
    Additional notes:
    
    zdb can now also decode the ZSTD compression header (flag -Z) and
    inspect the size, version and compression level saved in that header.
    For each record, if it is ZSTD compressed, the parameters of the decoded
    compression header get printed.
    
    ZSTD is included with all current tests and new tests are added
    as-needed.
    
    Per-dataset feature flags now get activated when the property is set.
    If a compression algorithm requires a feature flag, zfs activates the
    feature when the property is set, rather than waiting for the first
    block to be born.  This is currently only used by zstd but can be
    extended as needed.
    
    Closes: openzfs#6247
    Closes: openzfs#10277
    Closes: openzfs#9024
    Portions-Sponsored-By: The FreeBSD Foundation
    Co-authored-by: Allan Jude <[email protected]>
    Co-authored-by: Brian Behlendorf <[email protected]>
    Co-authored-by: Sebastian Gottschall <[email protected]>
    Co-authored-by: Kjeld Schouten-Lebbing <[email protected]>
    Co-authored-by: Michael Niewöhner <[email protected]>
    Signed-off-by: Allan Jude <[email protected]>
    Signed-off-by: Allan Jude <[email protected]>
    Signed-off-by: Brian Behlendorf <[email protected]>
    Signed-off-by: Sebastian Gottschall <[email protected]>
    Signed-off-by: Kjeld Schouten-Lebbing <[email protected]>
    Signed-off-by: Michael Niewöhner <[email protected]>
    5 people committed Aug 19, 2020
    Configuration menu
    Copy the full SHA
    3b12626 View commit details
    Browse the repository at this point in the history
  3. use ZSTD_getErrorCode() before comparing return values

    When we check that the error from a compression attempt is not
    ZSTD_error_dstSize_tooSmall, we need to first use ZSTD_getErrorCode()
    to turn the value into the correct enum, rather than a negative value.
    
    Not sure how this got lost earlier. I think maybe in the sidetracked
    kmem conversion.
    
    Sponsored-by: The FreeBSD Foundation
    Signed-off-by: Allan Jude <[email protected]>
    allanjude committed Aug 19, 2020
    Configuration menu
    Copy the full SHA
    51b8cb6 View commit details
    Browse the repository at this point in the history
  4. Update the zstd feature activation test to use its own pool

    Sponsored-by: The FreeBSD Foundation
    Signed-off-by: Allan Jude <[email protected]>
    allanjude committed Aug 19, 2020
    Configuration menu
    Copy the full SHA
    3a40ee7 View commit details
    Browse the repository at this point in the history
  5. Merge pull request #22 from allanjude/openzfs_zstd_cleanup

    Fix test, and kstat bug
    c0d3z3r0 authored Aug 19, 2020
    Configuration menu
    Copy the full SHA
    3136de0 View commit details
    Browse the repository at this point in the history