05 Nov, 2011

1 commit


19 Apr, 2011

1 commit


19 Jan, 2011

1 commit


21 Oct, 2010

1 commit

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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
     
  • 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

  • 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


17 Jul, 2007

1 commit


16 Jul, 2007

2 commits


10 Jul, 2007

1 commit


14 Dec, 2006

1 commit

  • The BLK_DEV_SWIM_IOP driver has:
    - already been marked as BROKEN in 2.6.0 three years ago and
    - is still marked as BROKEN.

    Drivers that had been marked as BROKEN for such a long time seem to be
    unlikely to be revived in the forseeable future.

    But if anyone wants to ever revive this driver, the code is still
    present in the older kernel releases.

    Signed-off-by: Adrian Bunk
    Cc: Jens Axboe
    Acked-by: Geert Uytterhoeven
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Adrian Bunk
     

24 Mar, 2006

1 commit


04 Nov, 2005

1 commit


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds