1. 22 6月, 2005 3 次提交
    • N
      [PATCH] md: optimised resync using Bitmap based intent logging · 32a7627c
      NeilBrown 提交于
      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: NNeil Brown <neilb@cse.unsw.edu.au>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      32a7627c
    • N
      [PATCH] md: improve the interface to sync_request · 57afd89f
      NeilBrown 提交于
      1/ change the return value (which is number-of-sectors synced)
       from 'int' to 'sector_t'.
       The number of sectors is usually easily small enough to fit
       in an int, but if resync needs to abort, it may want to return
       the total number of remaining sectors, which could be large.
       Also errors cannot be returned as negative numbers now, so use
       0 instead
      2/ Add a 'skipped' return parameter to allow the array to report
       that it skipped the sectors.  This allows md to take this into account
       in the speed calculations.
       Currently there is no important skipping, but the bitmap-based-resync
       that is coming will use this.
      Signed-off-by: NNeil Brown <neilb@cse.unsw.edu.au>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      57afd89f
    • N
      [PATCH] md: improve locking on 'safemode' and move superblock writes · 06d91a5f
      NeilBrown 提交于
      When md marks the superblock dirty before a write, it calls
      generic_make_request (to write the superblock) from within
      generic_make_request (to write the first dirty block), which could cause
      problems later.
      
      With this patch, the superblock write is always done by the helper thread, and
      write request are delayed until that write completes.
      
      Also, the locking around marking the array dirty and writing the superblock is
      improved to avoid possible races.
      Signed-off-by: NNeil Brown <neilb@cse.unsw.edu.au>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      06d91a5f
  2. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4
新手
引导
客服 返回
顶部