1. 25 6月, 2015 1 次提交
  2. 01 4月, 2015 1 次提交
  3. 17 2月, 2015 1 次提交
    • M
      brd: rename XIP to DAX · a7a97fc9
      Matthew Wilcox 提交于
      Since this is relating to FS_XIP, not KERNEL_XIP, it should be called
      DAX instead of XIP.
      Signed-off-by: NMatthew Wilcox <matthew.r.wilcox@intel.com>
      Cc: Andreas Dilger <andreas.dilger@intel.com>
      Cc: Boaz Harrosh <boaz@plexistor.com>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Dave Chinner <david@fromorbit.com>
      Cc: Jan Kara <jack@suse.cz>
      Cc: Jens Axboe <axboe@kernel.dk>
      Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
      Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
      Cc: Randy Dunlap <rdunlap@infradead.org>
      Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
      Cc: Theodore Ts'o <tytso@mit.edu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a7a97fc9
  4. 31 1月, 2014 1 次提交
    • M
      zram: promote zram from staging · cd67e10a
      Minchan Kim 提交于
      Zram has lived in staging for a LONG LONG time and have been
      fixed/improved by many contributors so code is clean and stable now.  Of
      course, there are lots of product using zram in real practice.
      
      The major TV companys have used zram as swap since two years ago and
      recently our production team released android smart phone with zram
      which is used as swap, too and recently Android Kitkat start to use zram
      for small memory smart phone.  And there was a report Google released
      their ChromeOS with zram, too and cyanogenmod have been used zram long
      time ago.  And I heard some disto have used zram block device for tmpfs.
      In addition, I saw many report from many other peoples.  For example,
      Lubuntu start to use it.
      
      The benefit of zram is very clear.  With my experience, one of the
      benefit was to remove jitter of video application with backgroud memory
      pressure.  It would be effect of efficient memory usage by compression
      but more issue is whether swap is there or not in the system.  Recent
      mobile platforms have used JAVA so there are many anonymous pages.  But
      embedded system normally are reluctant to use eMMC or SDCard as swap
      because there is wear-leveling and latency issues so if we do not use
      swap, it means we can't reclaim anoymous pages and at last, we could
      encounter OOM kill.  :(
      
      Although we have real storage as swap, it was a problem, too.  Because
      it sometime ends up making system very unresponsible caused by slow swap
      storage performance.
      
      Quote from Luigi on Google
       "Since Chrome OS was mentioned: the main reason why we don't use swap
        to a disk (rotating or SSD) is because it doesn't degrade gracefully
        and leads to a bad interactive experience.  Generally we prefer to
        manage RAM at a higher level, by transparently killing and restarting
        processes.  But we noticed that zram is fast enough to be competitive
        with the latter, and it lets us make more efficient use of the
        available RAM.  " and he announced.
      http://www.spinics.net/lists/linux-mm/msg57717.html
      
      Other uses case is to use zram for block device.  Zram is block device
      so anyone can format the block device and mount on it so some guys on
      the internet start zram as /var/tmp.
      http://forums.gentoo.org/viewtopic-t-838198-start-0.html
      
      Let's promote zram and enhance/maintain it instead of removing.
      Signed-off-by: NMinchan Kim <minchan@kernel.org>
      Reviewed-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      Acked-by: NNitin Gupta <ngupta@vflare.org>
      Acked-by: NPekka Enberg <penberg@kernel.org>
      Cc: Bob Liu <bob.liu@oracle.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Hugh Dickins <hughd@google.com>
      Cc: Jens Axboe <axboe@kernel.dk>
      Cc: Luigi Semenzato <semenzato@google.com>
      Cc: Mel Gorman <mgorman@suse.de>
      Cc: Rik van Riel <riel@redhat.com>
      Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd67e10a
  5. 24 1月, 2014 1 次提交
  6. 09 11月, 2013 2 次提交
  7. 25 10月, 2013 1 次提交
  8. 25 9月, 2013 1 次提交
  9. 19 6月, 2013 1 次提交
  10. 12 3月, 2013 1 次提交
  11. 05 2月, 2013 1 次提交
  12. 05 1月, 2013 1 次提交
    • P
      block: delete super ancient PC-XT driver for 1980's hardware · d1a6f4f1
      Paul Gortmaker 提交于
      This driver was for the 8 bit ISA cards that were installed in
      the PC-XT machines of 1980 vintage.  They supported the dual
      ribbon cable MFM drives of 10-20MB capacity, and ran at a 3:1
      interleave, giving performance on the order of 128kB/s.
      
      By the introduction of the PC-AT (286) these controllers were
      already scrapped in favour of 16 bit controllers with some onboard
      RAM that could support a 1:1 interleave.
      
      The git history doesn't show any evidence of runtime fixes that
      would reflect active usage; instead just the usual tree-wide API
      type changes/cleanups.  Going back to in-source changelogs, the
      last "runtime" fix that is evident is something I did over a
      dozen years ago[1] -- and even back then, the hardware was long
      since unavailable, so that ancient fix was also not runtime tested.
      
      The time is long overdue for this to get flushed, so lets get
      rid of it before anyone wastes more time doing builds and sparse
      checks etc. on long since dead code.
      
      [1] http://lkml.indiana.edu/hypermail/linux/kernel/0102.2/0027.htmlSigned-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      d1a6f4f1
  13. 30 10月, 2012 1 次提交
  14. 24 10月, 2012 1 次提交
    • K
      drivers/block: remove CONFIG_EXPERIMENTAL · b8977285
      Kees Cook 提交于
      This config item has not carried much meaning for a while now and is
      almost always enabled by default. As agreed during the Linux kernel
      summit, remove it.
      
      CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      CC: Asai Thambi S P <asamymuthupa@micron.com>
      CC: Pete Zaitcev <zaitcev@redhat.com>
      CC: Cong Wang <xiyou.wangcong@gmail.com>
      CC: Jens Axboe <jaxboe@fusionio.com>
      Signed-off-by: NKees Cook <keescook@chromium.org>
      Signed-off-by: NJens Axboe <axboe@kernel.dk>
      b8977285
  15. 06 9月, 2012 1 次提交
  16. 17 3月, 2012 1 次提交
  17. 05 11月, 2011 2 次提交
  18. 09 8月, 2011 1 次提交
  19. 01 8月, 2011 1 次提交
  20. 13 5月, 2011 1 次提交
  21. 19 4月, 2011 1 次提交
  22. 06 1月, 2011 1 次提交
  23. 21 10月, 2010 1 次提交
  24. 09 6月, 2010 1 次提交
  25. 07 6月, 2010 1 次提交
  26. 11 5月, 2010 1 次提交
  27. 02 10月, 2009 1 次提交
  28. 24 6月, 2009 1 次提交
    • J
      osdblk: a Linux block device for OSD objects · 2a13877c
      Jeff Garzik 提交于
      Submitted driver exports a block device of the form /dev/osdblkX,
      where X is a decimal number.
      
      It does that by mounting a stacking block device on top
      of an osd object. For example, if you create a 2G object
      on an OSD device, you can then use this module to present
      that 2G object as a Linux block device.
      
      See inside patch for exact documentation.
      
      [Sitting at linux-next helped fix proper Kconfig dependency
       for this driver, thanks to Randy Dunlap]
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      2a13877c
  29. 13 6月, 2009 1 次提交
  30. 21 5月, 2009 1 次提交
  31. 28 4月, 2009 1 次提交
  32. 07 4月, 2009 1 次提交
    • U
      mflash: initial support · 3fbed4c6
      unsik Kim 提交于
      This driver supports mflash IO mode for linux.
      
      Mflash is embedded flash drive and mainly targeted mobile and consumer
      electronic devices.
      
      Internally, mflash has nand flash and other hardware logics and supports 2
      different operation (ATA, IO) modes.  ATA mode doesn't need any new driver
      and currently works well under standard IDE subsystem.  Actually it's one
      chip SSD.  IO mode is ATA-like custom mode for the host that doesn't have
      IDE interface.
      
      Followings are brief descriptions about IO mode.
      A. IO mode based on ATA protocol and uses some custom command. (read confirm,
      write confirm)
      B. IO mode uses SRAM bus interface.
      C. IO mode supports 4kB boot area, so host can boot from mflash.
      
      This driver is quitely similar to a standard ATA driver, but because of
      following reasons it is currently seperated with ATA layer.
      
      1. ATA layer deals standard ATA protocol.  ATA layer have many low-
         level device specific interface, but data transfer keeps ATA rule.
         But, mflash IO mode doesn't.
      
      2. Even though currently not used in mflash driver code, mflash has
         some custom command and modes.  (nand fusing, firmware patch, etc) If
         this feature supported in linux kernel, ATA layer more altered.
      
      3. Currently PATA platform device driver doesn't support interrupt.
         (I'm not sure) But, mflash uses interrupt (polling mode is just for
         debug).
      
      4. mflash is somewhat under-develop product.  Even though some company
         already using mflash their own product, I think more time is needed for
         standardization of custom command and mode.  That time (maybe October)
         I will talk to with ATA people.  If they accept integration, I will
         integrate.
      Signed-off-by: Nunsik Kim <donari75@gmail.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      3fbed4c6
  33. 27 3月, 2009 1 次提交
  34. 07 1月, 2009 1 次提交
  35. 06 1月, 2009 1 次提交
  36. 05 1月, 2009 1 次提交
    • A
      bzip2/lzma: config and initramfs support for bzip2/lzma decompression · 30d65dbf
      Alain Knaff 提交于
      Impact: New code for initramfs decompression, new features
      
      This is the second part of the bzip2/lzma patch
      
      The bzip patch is based on an idea by Christian Ludwig, includes support for
      compressing the kernel with bzip2 or lzma rather than gzip. Both
      compressors give smaller sizes than gzip.  Lzma's decompresses faster
      than bzip2.
      
      It also supports ramdisks and initramfs' compressed using these two
      compressors.
      
      The functionality has been successfully used for a couple of years by
      the udpcast project
      
      This version applies to "tip" kernel 2.6.28
      
      This part contains:
      - support for new compressions (bzip2 and lzma) in initramfs and
      old-style ramdisk
      - config dialog for kernel compression (but new kernel compressions
      not yet supported)
      Signed-off-by: NAlain Knaff <alain@knaff.lu>
      Signed-off-by: NH. Peter Anvin <hpa@zytor.com>
      30d65dbf
  37. 15 11月, 2008 1 次提交
  38. 17 7月, 2008 1 次提交