Eric Lee / smarc-fsl-linux-kernel

19 Apr, 2017

1 commit

15 Apr, 2017

1 commit

  • 842533949   remove the mg_disk driver ... Browse Code »

    This drivers was added in 2008, but as far as a I can tell we never had a
    single platform that actually registered resources for the platform driver.

    It's also been unmaintained for a long time and apparently has a ATA mode
    that can be driven using the IDE/libata subsystem.

    Signed-off-by: Christoph Hellwig
    Reviewed-by: Hannes Reinecke
    Signed-off-by: Jens Axboe

    Christoph Hellwig
     

05 Apr, 2017

1 commit

  • 8e14be53f   remove the obsolete hd driver ... Browse Code »

    This driver is for pre-IDE hardisk that are only found in PC from the
    stoneage of personal computing, and which we don't support elsewhere
    in the kernel these days.

    It's also been marked broken forever.

    Signed-off-by: Christoph Hellwig
    Reviewed-by: Martin K. Petersen
    Signed-off-by: Jens Axboe

    Christoph Hellwig
     

16 Mar, 2016

1 commit

10 Oct, 2015

1 commit

  • 57dacad5f   nvme: move to a new drivers/nvme/host directory ... Browse Code »

    This patch moves the NVMe driver from drivers/block/ to its own new
    drivers/nvme/host/ directory. This is in preparation of splitting the
    current monolithic driver up and add support for the upcoming NVMe
    over Fabrics standard. The drivers/nvme/host/ is chose to leave space
    for a NVMe target implementation in addition to this host side driver.

    Signed-off-by: Jay Sternberg
    [hch: rebased, renamed core.c to pci.c, slight tweaks]
    Signed-off-by: Christoph Hellwig
    Acked-by: Keith Busch
    Signed-off-by: Jens Axboe

    Jay Sternberg
     

25 Jun, 2015

1 commit

01 Apr, 2015

1 commit

  • 9e853f231   drivers/block/pmem: Add a driver for persistent memory ... Browse Code »

    PMEM is a new driver that presents a reserved range of memory as
    a block device. This is useful for developing with NV-DIMMs,
    and can be used with volatile memory as a development platform.

    This patch contains the initial driver from Ross Zwisler, with
    various changes: converted it to use a platform_device for
    discovery, fixed partition support and merged various patches
    from Boaz Harrosh.

    Tested-by: Ross Zwisler
    Signed-off-by: Ross Zwisler
    Signed-off-by: Christoph Hellwig
    Acked-by: Dan Williams
    Cc: Andrew Morton
    Cc: Andy Lutomirski
    Cc: Boaz Harrosh
    Cc: Borislav Petkov
    Cc: H. Peter Anvin
    Cc: Jens Axboe
    Cc: Jens Axboe
    Cc: Keith Busch
    Cc: Linus Torvalds
    Cc: Matthew Wilcox
    Cc: Thomas Gleixner
    Cc: linux-nvdimm@ml01.01.org
    Link: http://lkml.kernel.org/r/1427872339-6688-3-git-send-email-hch@lst.de
    [ Minor cleanups. ]
    Signed-off-by: Ingo Molnar

    Ross Zwisler
     

31 Jan, 2014

1 commit

  • cd67e10ac   zram: promote zram from staging ... Browse Code »

    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
    Reviewed-by: Konrad Rzeszutek Wilk
    Acked-by: Nitin Gupta
    Acked-by: Pekka Enberg
    Cc: Bob Liu
    Cc: Greg Kroah-Hartman
    Cc: Hugh Dickins
    Cc: Jens Axboe
    Cc: Luigi Semenzato
    Cc: Mel Gorman
    Cc: Rik van Riel
    Cc: Seth Jennings
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Minchan Kim
     

19 Dec, 2013

1 commit

04 Dec, 2013

1 commit

14 Nov, 2013

1 commit

  • 5eea9be8b   Merge branch 'for-3.13/drivers' of git://git.kernel.dk/linux-block ... Browse Code »

    Pull block driver updates from Jens Axboe:
    "This is the block driver pull request for 3.13. As with the core pull
    request just sent out, this was rebased on top of the core branch
    again after the immutable series was pulled. This also means that
    bcache gets to sit the initial pull over. I will send a second driver
    pull request in the merge window to get those fixes in, once they have
    been rebased and tested on top of the non-immutable stack.

    This pull request contains:

    - Add support for the sTec Kronos pci-e flash card from sTec. Also
    has various cleanups for this driver, from myself, Bart, Mike
    Snizter, and Wei Yongjun.

    - Add surprise removal support for the micron mtip32xx driver from
    Micron.

    - Floppy documentation fix from Ben Harris.

    - debugfs bug fix for pktcdvd from Dan Carpenter.

    - Fix for the mtip32xx driver stack usage in the debugfs path,
    dynamically allocating those buffers instead. From David Milburn.

    - Disable cpqarray in Kconfig. The plan is to remove it on request
    of HP, but lets disable it for a few revisions just to see if
    anyone yells.

    - drbd fixes from Lars Ellenberg and Philipp Reisner.

    - Elevator switch fix for the s390 block driver from Heiko Carstens.

    - loop crash fix on IO to unassigned device from Mikulas Patocka.

    - A series of bug fixes for the IBM rsxx pci-e flash driver from
    Philip J Kelleher.

    - cciss probe fix from Stephen Cameron.

    - Xen block front/back fixes from Roger Pau Monne and Vegard Nossum"

    * 'for-3.13/drivers' of git://git.kernel.dk/linux-block: (41 commits)
    floppy: Correct documentation of driver options when used as a module.
    pktcdvd: debugfs functions return NULL on error
    xen-blkfront: restore the non-persistent data path
    skd: fix formatting in skd_s1120.h
    skd: reorder construct/destruct code
    skd: cleanup skd_do_inq_page_da()
    skd: remove SKD_OMIT_FROM_SRC_DIST ifdefs
    skd: remove redundant skdev->pdev assignment from skd_pci_probe()
    skd: use
    skd: remove SCSI subsystem specific includes
    skd: register block device only if some devices are present
    skd: fix error messages in skd_init()
    skd: fix error paths in skd_init()
    skd: fix unregister_blkdev() placement
    skd: more removal of bio-based code
    skd: cleanup the skd_*() function block wrapping
    skd: rip out bio path
    skd: fix error return code in skd_pci_probe()
    s390/dasd: hold request queue sysfs lock when calling elevator_init()
    cciss: return 0 from driver probe function on success, not 1
    ...

    Linus Torvalds
     

09 Nov, 2013

1 commit

25 Oct, 2013

1 commit

29 Mar, 2013

1 commit

  • 5d0f6131a   NVMe: Add nvme-scsi.c ... Browse Code »

    Translates SCSI commands in SG_IO ioctl to NVMe commands.
    Uses the scsi-nvme translation spec from nvmexpress.org as reference.

    Signed-off-by: Vishal Verma
    Signed-off-by: Matthew Wilcox

    Vishal Verma
     

27 Mar, 2013

1 commit

14 Feb, 2013

1 commit

  • ec8edc764   Merge branch 'delete-xt-disk' of git://git.kernel.org/pub/scm/linux/kernel/git/p… ... Browse Code »

    …aulg/linux into for-3.9/drivers

    Paul writes:

    Please pull the following to get the removal of the original IBM PC-XT
    hard disk driver from the block layer (drivers/block/xd.c).

    As near as I can tell, it hasn't seen a run time fix in over a dozen
    years, and with drive sizes of 10-20MB, and performance of about 128kB/s
    maximum, it is no surprise that it has been completely unused for well
    over a decade.

    The removal was originally posted[1] well over a month ago, and since
    then, there has been nobody objecting to the removal, aside from someone
    who had mistakenly confused it with a completely different driver (hd.c)

    Jens Axboe
     

05 Feb, 2013

1 commit

05 Jan, 2013

1 commit

  • d1a6f4f19   block: delete super ancient PC-XT driver for 1980's hardware ... Browse Code »

    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.html

    Signed-off-by: Paul Gortmaker

    Paul Gortmaker
     

06 Sep, 2012

1 commit

19 Jan, 2012

1 commit

  • 92b5abbb4   Merge git://git.infradead.org/users/willy/linux-nvme ... Browse Code »

    * git://git.infradead.org/users/willy/linux-nvme: (105 commits)
    NVMe: Set number of queues correctly
    NVMe: Version 0.8
    NVMe: Set queue flags correctly
    NVMe: Simplify nvme_unmap_user_pages
    NVMe: Mark the end of the sg list
    NVMe: Fix DMA mapping for admin commands
    NVMe: Rename IO_TIMEOUT to NVME_IO_TIMEOUT
    NVMe: Merge the nvme_bio and nvme_prp data structures
    NVMe: Change nvme_completion_fn to take a dev
    NVMe: Change get_nvmeq to take a dev instead of a namespace
    NVMe: Simplify completion handling
    NVMe: Update Identify Controller data structure
    NVMe: Implement doorbell stride capability
    NVMe: Version 0.7
    NVMe: Don't probe namespace 0
    Fix calculation of number of pages in a PRP List
    NVMe: Create nvme_identify and nvme_get_features functions
    NVMe: Fix memory leak in nvme_dev_add()
    NVMe: Fix calls to dma_unmap_sg
    NVMe: Correct sg list setup in nvme_map_user_pages
    ...

    Linus Torvalds
     

05 Nov, 2011

2 commits

19 Apr, 2011

1 commit

19 Jan, 2011

1 commit

21 Oct, 2010

1 commit

  • 602adf400   rbd: introduce rados block device (rbd), based on libceph ... Browse Code »

    The rados block device (rbd), based on osdblk, creates a block device
    that is backed by objects stored in the Ceph distributed object storage
    cluster. Each device consists of a single metadata object and data
    striped over many data objects.

    The rbd driver supports read-only snapshots.

    Signed-off-by: Yehuda Sadeh
    Signed-off-by: Sage Weil

    Yehuda Sadeh
     

02 Oct, 2009

1 commit

24 Jun, 2009

1 commit

  • 2a13877c5   osdblk: a Linux block device for OSD objects ... Browse Code »

    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: Jeff Garzik
    Signed-off-by: Boaz Harrosh

    Jeff Garzik
     

07 Apr, 2009

1 commit

  • 3fbed4c61   mflash: initial support ... Browse Code »

    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
    Cc: Alan Cox
    Signed-off-by: Andrew Morton
    Signed-off-by: Jens Axboe

    unsik Kim
     

27 Mar, 2009

1 commit

13 Mar, 2009

1 commit

  • f507cd220   ps3/block: Replace mtd/ps3vram by block/ps3vram ... Browse Code »

    Convert the PS3 Video RAM Storage Driver from an MTD driver to a plain block
    device driver.

    The ps3vram driver exposes unused video RAM on the PS3 as a block device
    suitable for storage or swap. Fast data transfer is achieved using a local
    cache in system RAM and DMA transfers via the GPU.

    The new driver is ca. 50% faster for reading, and ca. 10% for writing.

    Signed-off-by: Geert Uytterhoeven
    Acked-by: Geoff Levand
    Signed-off-by: Benjamin Herrenschmidt

    Geert Uytterhoeven
     

17 Jul, 2008

1 commit

17 Mar, 2008

1 commit

09 Feb, 2008

1 commit

  • 9db5579be   rewrite rd ... Browse Code »

    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
    Signed-off-by: Byron Bradley
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Nick Piggin
     

23 Oct, 2007

2 commits

  • 0ca49ca94   Remove old lguest bus and drivers. ... Browse Code »

    This gets rid of the lguest bus, drivers and DMA mechanism, to make
    way for a generic virtio mechanism.

    Signed-off-by: Rusty Russell

    Rusty Russell
     
  • e467cde23   Block driver using virtio. ... Browse Code »

    The block driver uses scatter-gather lists with sg[0] being the
    request information (struct virtio_blk_outhdr) with the type, sector
    and inbuf id. The next N sg entries are the bio itself, then the last
    sg is the status byte. Whether the N entries are in or out depends on
    whether it's a read or a write.

    We accept the normal (SCSI) ioctls: they get handed through to the other
    side which can then handle it or reply that it's unsupported. It's
    not clear that this actually works in general, since I don't know
    if blk_pc_request() requests have an accurate rq_data_dir().

    Although we try to reply -ENOTTY on unsupported commands, ioctl(fd,
    CDROMEJECT) returns success to userspace. This needs a separate
    patch.

    Signed-off-by: Rusty Russell
    Cc: Jens Axboe

    Rusty Russell
     

30 Jul, 2007

1 commit

22 Jul, 2007

1 commit

  • c6131fa52   ps3: Disk Storage Driver ... Browse Code »

    Add a Disk Storage Driver for the PS3:
    - Implemented as a block device driver with a dynamic major
    - Disk names (and partitions) are of the format ps3d%c(%u)
    - Uses software scatter-gather with a 64 KiB bounce buffer as the hypervisor
    doesn't support scatter-gather

    Cc: Geoff Levand
    Signed-off-by: Geert Uytterhoeven
    Acked-by: Jens Axboe
    Cc: James Bottomley
    Cc: Paul Mackerras
    Cc: Benjamin Herrenschmidt
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Geert Uytterhoeven
     

20 Jul, 2007

1 commit

18 Jul, 2007

2 commits