1. 21 Nov, 2015 2 commits
  2. 20 Nov, 2015 1 commit
  3. 18 Nov, 2015 1 commit
  4. 17 Nov, 2015 3 commits
  5. 16 Nov, 2015 1 commit
  6. 14 Nov, 2015 1 commit
  7. 11 Nov, 2015 1 commit
    • Jens Axboe's avatar
      MAINTAINERS: add reference to new linux-block list · 82c426e0
      Jens Axboe authored
      In the past, I've resisted doing a non-lkml related block/storage
      list. But we have more activity now than we previously did, and
      ain't nobody got time to track and follow lkml.
      
      So now linux-block@vger.kernel.org exists. Please CC your patches
      related to block/storage here, and we'll have an easier time
      tracking them.
      Signed-off-by: default avatarJens Axboe <axboe@fb.com>
      82c426e0
  8. 09 Nov, 2015 2 commits
  9. 07 Nov, 2015 2 commits
  10. 05 Nov, 2015 2 commits
  11. 03 Nov, 2015 1 commit
  12. 02 Nov, 2015 1 commit
  13. 31 Oct, 2015 1 commit
  14. 30 Oct, 2015 7 commits
  15. 29 Oct, 2015 1 commit
    • Matias Bjørling's avatar
      lightnvm: Support for Open-Channel SSDs · cd9e9808
      Matias Bjørling authored
      Open-channel SSDs are devices that share responsibilities with the host
      in order to implement and maintain features that typical SSDs keep
      strictly in firmware. These include (i) the Flash Translation Layer
      (FTL), (ii) bad block management, and (iii) hardware units such as the
      flash controller, the interface controller, and large amounts of flash
      chips. In this way, Open-channels SSDs exposes direct access to their
      physical flash storage, while keeping a subset of the internal features
      of SSDs.
      
      LightNVM is a specification that gives support to Open-channel SSDs
      LightNVM allows the host to manage data placement, garbage collection,
      and parallelism. Device specific responsibilities such as bad block
      management, FTL extensions to support atomic IOs, or metadata
      persistence are still handled by the device.
      
      The implementation of LightNVM consists of two parts: core and
      (multiple) targets. The core implements functionality shared across
      targets. This is initialization, teardown and statistics. The targets
      implement the interface that exposes physical flash to user-space
      applications. Examples of such targets include key-value store,
      object-store, as well as traditional block devices, which can be
      application-specific.
      
      Contributions in this patch from:
      
        Javier Gonzalez <jg@lightnvm.io>
        Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
        Jesper Madsen <jmad@itu.dk>
      Signed-off-by: default avatarMatias Bjørling <m@bjorling.me>
      Signed-off-by: default avatarJens Axboe <axboe@fb.com>
      cd9e9808
  16. 28 Oct, 2015 5 commits
  17. 27 Oct, 2015 2 commits
  18. 26 Oct, 2015 1 commit
  19. 23 Oct, 2015 4 commits
  20. 21 Oct, 2015 1 commit