Announcement

Collapse
No announcement yet.

Reiser4 Updated For The Linux 3.18 Kernel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Reiser4 Updated For The Linux 3.18 Kernel

    Phoronix: Reiser4 Updated For The Linux 3.18 Kernel

    For those still relying upon the Reiser4 file-system and haven't migrated off to ZFS On Linux or Btrfs, the out-of-tree Reiser4 kernel code has been updated for compatibility with the Linux 3.18 kernel...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    It would be a lot of fun to fund the Reiser4 team completely, but with two demands for the funding:

    1) Rename it to your own name (or something else, like DarthVaderFS)
    2) The code should be completely re-written to fully comply with the kernel code standard, so it can be mainlined within one or two (or some other fairly low but reasonable number from a "how long does it take to rewrite") releases.

    Oooh, the entertainment!

    Comment


    • #3
      Maybe some update is in order?

      The developers still involved with Reiser4 are mostly doing bug-fixes and maintaining support for new kernel versions without seeing much in the way of new feature development.
      I'd just like to point out these new major Reiser4 features added in last 12 months:

      March 2014: Different Transaction Models - Unique feature among Linux FSes
      Every R4 partition can be mounted as COW, Journaled or Hybrid mode so now Reiser4 can be Journaled, COW or Hybrid (default) filesystem to suit different storage devices.

      May 2014: Discard support - Online TRIM

      August 2014: Batch discard support - Offline TRIM (FITRIM)

      February 2015: Precise real-time discard for SSD devices - TRIM - Unique feature among Linux FSes
      When executing online trim FSes generate garbage over time since erase units in general don't coincide with file system blocks. Precise real-time discard for Reiser4 doesn't generate garbage.

      February 2015: Metadata checksums
      This is a nice example how you can easily change disk format in Reiser4 without breaking backward compatibility.

      Special patch for 3.18 wasn't needed as patch for works and applies OK. Patch for 3.19 exists in git tree.

      Would be nice to have some benchmarks on Phoronix of Reiser4 in journaled, cow and hybrid mode on SSD and HDD, with and without compression and with different IO schedulers.

      One interesting benchmark for Linux FSes on SSD would be: How long it takes for a FS to get SSD to have a performance drop because it uses up all free blocks and having to perform a read-modify-write for all subsequent writes (write amplification goes up, performance goes down).
      Here's a nice explanation of the effect from Anandtech.
      FSes better optimized for SSDs will take longer. Wouldn't be hard to set up, just have a reproducible write intensive test and compare amount of written data until drop in write speed.

      Comment


      • #4
        Maybe some update is in order?

        The developers still involved with Reiser4 are mostly doing bug-fixes and maintaining support for new kernel versions without seeing much in the way of new feature development.
        I'd just like to point out these new major Reiser4 features added in last 12 months:

        March 2014: Different Transaction Models - Unique feature among Linux FSes
        Every R4 partition can be mounted as COW, Journaled or Hybrid mode so now Reiser4 can be Journaled, COW or Hybrid (default) filesystem to suit different storage devices.

        May 2014: Discard support - Online TRIM

        August 2014: Batch discard support - Offline TRIM (FITRIM)

        February 2015: Precise real-time discard for SSD devices - TRIM - Unique feature among Linux FSes
        When executing online trim FSes generate garbage over time since erase units in general don't coincide with file system blocks. Precise real-time discard for Reiser4 doesn't generate garbage.

        February 2015: Metadata checksums
        This is a nice example how you can easily change disk format in Reiser4 without breaking backward compatibility.

        Special patch for 3.18 wasn't needed as patch for works and applies OK. Patch for 3.19 exists in git tree.

        Would be nice to have some benchmarks on Phoronix of Reiser4 in journaled, cow and hybrid mode on SSD and HDD, with and without compression and with different IO schedulers.

        One interesting benchmark for Linux FSes on SSD would be: How long it takes for a FS to get SSD to have a performance drop because it uses up all free blocks and having to perform a read-modify-write for all subsequent writes (write amplification goes up, performance goes down).
        Here's a nice explanation of the effect from Anandtech.
        FSes better optimized for SSDs will take longer. Wouldn't be hard to set up, just have a reproducible write intensive test and compare amount of written data until drop in write speed.

        Comment

        Working...
        X