Announcement

Collapse
No announcement yet.

A New Log-Structured Linux Caching Software Driver

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

  • A New Log-Structured Linux Caching Software Driver

    Phoronix: A New Log-Structured Linux Caching Software Driver

    While it didn't make it as part of the initial staging pull for the Linux 3.12 merge window, on Sunday dm-writeboost was proposed for staging. DM-Writeboost is new log-structured Linux caching software...

    http://www.phoronix.com/vr.php?view=MTQ1Mjg

  • #2
    Atomicity?

    Does this negatively affect atomicity?
    Atomic disk operations, like ACID compliance in databases.

    Comment


    • #3
      My guess is it positively affects it, as writing out changes sequentially tends to let the software order things the right way without much effort. I'm imagining this works like an overgrown journal on ext3 or similar, but I don't really know exactly.

      Comment


      • #4
        Originally posted by BradN View Post
        My guess is it positively affects it, as writing out changes sequentially tends to let the software order things the right way without much effort. I'm imagining this works like an overgrown journal on ext3 or similar, but I don't really know exactly.
        But what if the software writes something to the disk, then later the power goes out.
        Now the writes were never committed to the disk, they were in the cache and actually never written.

        Comment


        • #5
          Originally posted by uid313 View Post
          But what if the software writes something to the disk, then later the power goes out.
          Now the writes were never committed to the disk, they were in the cache and actually never written.
          Disks use SCSI commands like FUA and FLUSH for barriers (ordering) and durability. Looking at the dm-writeboost pdf, it implements these commands by waiting for the SSD to return from a similar command. Barring bugs or exposure of the uncached device, filesystems will behave correctly. Reliability is lower since there are two points of failure (SSD and HDD), but you should be backing up regardless of how much hardware is involved.

          Comment


          • #6
            Originally posted by Tobu View Post
            Disks use SCSI commands like FUA and FLUSH for barriers (ordering) and durability. Looking at the dm-writeboost pdf, it implements these commands by waiting for the SSD to return from a similar command. Barring bugs or exposure of the uncached device, filesystems will behave correctly. Reliability is lower since there are two points of failure (SSD and HDD), but you should be backing up regardless of how much hardware is involved.
            The thing about ACID and atomic operations is that they're supposed to be guaranteed.

            Comment


            • #7
              Originally posted by uid313 View Post
              The thing about ACID and atomic operations is that they're supposed to be guaranteed.
              You failed to read the short technical explanation, so here's a tl;dr. dm-writeboost doesn't change a thing for databases.

              Comment

              Working...
              X