2005-04-16 16:20:36 -06:00
|
|
|
#
|
|
|
|
|
# Makefile for the kernel block device drivers.
|
|
|
|
|
#
|
|
|
|
|
# 12 June 2000, Christoph Hellwig <hch@infradead.org>
|
|
|
|
|
# Rewritten to use lists instead of if-statements.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_MAC_FLOPPY) += swim3.o
|
2008-11-15 08:10:10 -07:00
|
|
|
obj-$(CONFIG_BLK_DEV_SWIM) += swim_mod.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_FD) += floppy.o
|
|
|
|
|
obj-$(CONFIG_AMIGA_FLOPPY) += amiflop.o
|
2007-07-21 05:37:45 -06:00
|
|
|
obj-$(CONFIG_PS3_DISK) += ps3disk.o
|
2009-03-05 19:54:09 -07:00
|
|
|
obj-$(CONFIG_PS3_VRAM) += ps3vram.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_ATARI_FLOPPY) += ataflop.o
|
|
|
|
|
obj-$(CONFIG_AMIGA_Z2RAM) += z2ram.o
|
rewrite rd
This is a rewrite of the ramdisk block device driver.
The old one is really difficult because it effectively implements a block
device which serves data out of its own buffer cache. It relies on the dirty
bit being set, to pin its backing store in cache, however there are non
trivial paths which can clear the dirty bit (eg. try_to_free_buffers()),
which had recently lead to data corruption. And in general it is completely
wrong for a block device driver to do this.
The new one is more like a regular block device driver. It has no idea about
vm/vfs stuff. It's backing store is similar to the buffer cache (a simple
radix-tree of pages), but it doesn't know anything about page cache (the pages
in the radix tree are not pagecache pages).
There is one slight downside -- direct block device access and filesystem
metadata access goes through an extra copy and gets stored in RAM twice.
However, this downside is only slight, because the real buffercache of the
device is now reclaimable (because we're not playing crazy games with it), so
under memory intensive situations, footprint should effectively be the same --
maybe even a slight advantage to the new driver because it can also reclaim
buffer heads.
The fact that it now goes through all the regular vm/fs paths makes it
much more useful for testing, too.
text data bss dec hex filename
2837 849 384 4070 fe6 drivers/block/rd.o
3528 371 12 3911 f47 drivers/block/brd.o
Text is larger, but data and bss are smaller, making total size smaller.
A few other nice things about it:
- Similar structure and layout to the new loop device handlinag.
- Dynamic ramdisk creation.
- Runtime flexible buffer head size (because it is no longer part of the
ramdisk code).
- Boot / load time flexible ramdisk size, which could easily be extended
to a per-ramdisk runtime changeable size (eg. with an ioctl).
- Can use highmem for the backing store.
[akpm@linux-foundation.org: fix build]
[byron.bbradley@gmail.com: make rd_size non-static]
Signed-off-by: Nick Piggin <npiggin@suse.de>
Signed-off-by: Byron Bradley <byron.bbradley@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-02-08 05:19:49 -07:00
|
|
|
obj-$(CONFIG_BLK_DEV_RAM) += brd.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_LOOP) += loop.o
|
|
|
|
|
obj-$(CONFIG_BLK_CPQ_DA) += cpqarray.o
|
|
|
|
|
obj-$(CONFIG_BLK_CPQ_CISS_DA) += cciss.o
|
|
|
|
|
obj-$(CONFIG_BLK_DEV_DAC960) += DAC960.o
|
2007-07-17 05:03:39 -06:00
|
|
|
obj-$(CONFIG_XILINX_SYSACE) += xsysace.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_CDROM_PKTCDVD) += pktcdvd.o
|
mflash: initial support
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: unsik Kim <donari75@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
2009-04-02 13:50:58 -06:00
|
|
|
obj-$(CONFIG_MG_DISK) += mg_disk.o
|
2007-07-16 05:03:56 -06:00
|
|
|
obj-$(CONFIG_SUNVDC) += sunvdc.o
|
2011-01-20 10:50:14 -07:00
|
|
|
obj-$(CONFIG_BLK_DEV_NVME) += nvme.o
|
2013-10-15 14:19:07 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_SKD) += skd.o
|
2009-04-10 05:50:45 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_OSD) += osdblk.o
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
|
obj-$(CONFIG_BLK_DEV_UMEM) += umem.o
|
|
|
|
|
obj-$(CONFIG_BLK_DEV_NBD) += nbd.o
|
|
|
|
|
obj-$(CONFIG_BLK_DEV_CRYPTOLOOP) += cryptoloop.o
|
2007-10-21 19:03:38 -06:00
|
|
|
obj-$(CONFIG_VIRTIO_BLK) += virtio_blk.o
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
|
obj-$(CONFIG_BLK_DEV_SX8) += sx8.o
|
2008-07-16 12:33:47 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_HD) += hd.o
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-07-17 19:37:06 -06:00
|
|
|
obj-$(CONFIG_XEN_BLKDEV_FRONTEND) += xen-blkfront.o
|
2011-04-18 12:24:23 -06:00
|
|
|
obj-$(CONFIG_XEN_BLKDEV_BACKEND) += xen-blkback/
|
2009-09-25 17:07:19 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_DRBD) += drbd/
|
2010-08-12 17:11:25 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_RBD) += rbd.o
|
2011-08-30 08:34:26 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_PCIESSD_MTIP32XX) += mtip32xx/
|
2008-11-15 08:10:10 -07:00
|
|
|
|
2013-02-05 06:15:02 -07:00
|
|
|
obj-$(CONFIG_BLK_DEV_RSXX) += rsxx/
|
2013-10-25 04:52:25 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_NULL_BLK) += null_blk.o
|
zram: promote zram from staging
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: Minchan Kim <minchan@kernel.org>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Acked-by: Nitin Gupta <ngupta@vflare.org>
Acked-by: Pekka 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: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-01-30 16:45:52 -07:00
|
|
|
obj-$(CONFIG_ZRAM) += zram/
|
2013-02-05 06:15:02 -07:00
|
|
|
|
2013-03-04 18:40:58 -07:00
|
|
|
nvme-y := nvme-core.o nvme-scsi.o
|
2013-10-15 14:19:07 -06:00
|
|
|
skd-y := skd_main.o
|
2011-01-19 08:25:02 -07:00
|
|
|
swim_mod-y := swim.o swim_asm.o
|