Eric Lee / smarc-fsl-linux-kernel

31 Mar, 2009

2 commits

  • 92022950c   md: move most content from md.h to md_k.h ... Browse Code »

    The extern function definitions are kernel-internal definitions, so
    they belong in md_k.h

    The MD_*_VERSION values could reasonably go in a number of places,
    but md_u.h seems most reasonable.

    This leaves almost nothing in md.h. It will go soon.

    Signed-off-by: NeilBrown

    NeilBrown
     
  • 8b2b5c217   md: move LEVEL_* definition from md_k.h to md_u.h ... Browse Code »

    .. as they are part of the user-space interface.
    Also move MdpMinorShift into there so we can remove duplication.

    Lastly move mdp_major in. It is less obviously part of the user-space
    interface, but do_mounts_md.c uses it, and it is acting a bit like
    user-space.

    Signed-off-by: NeilBrown

    NeilBrown
     

03 Oct, 2006

1 commit

22 Jun, 2005

1 commit

  • 32a7627cf   [PATCH] md: optimised resync using Bitmap based intent logging ... Browse Code »

    With this patch, the intent to write to some block in the array can be logged
    to a bitmap file. Each bit represents some number of sectors and is set
    before any update happens, and only cleared when all writes relating to all
    sectors are complete.

    After an unclean shutdown, information in this bitmap can be used to optimise
    resync - only sectors which could be out-of-sync need to be updated.

    Also if a drive is removed and then added back into an array, the recovery can
    make use of the bitmap to optimise reconstruction. This is not implemented in
    this patch.

    Currently the bitmap is stored in a file which must (obviously) be stored on a
    separate device.

    The patch only provided infrastructure. It does not update any personalities
    to bitmap intent logging.

    Md arrays can still be used with no bitmap file. This patch has minimal
    impact on such arrays.

    Signed-off-by: Neil Brown
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    NeilBrown
     

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    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