1. 28 11月, 2007 1 次提交
  2. 04 10月, 2007 1 次提交
  3. 21 9月, 2007 1 次提交
    • M
      ocfs2: Allow smaller allocations during large writes · 415cb800
      Mark Fasheh 提交于
      The ocfs2 write code loops through a page much like the block code, except
      that ocfs2 allocation units can be any size, including larger than page
      size. Typically it's equal to or larger than page size - most kernels run 4k
      pages, the minimum ocfs2 allocation (cluster) size.
      
      Some changes introduced during 2.6.23 changed the way writes to pages are
      handled, and inadvertantly broke support for > 4k page size. Instead of just
      writing one cluster at a time, we now handle the whole page in one pass.
      
      This means that multiple (small) seperate allocations might happen in the
      same pass. The allocation code howver typically optimizes by getting the
      maximum which was reserved. This triggered a BUG_ON in the extend code where
      it'd ask for a single bit (for one part of a > 4k page) and get back more
      than it asked for.
      
      Fix this by providing a variant of the high level allocation function which
      allows the caller to specify a maximum. The traditional function remains and
      just calls the new one with a maximum determined from the initial
      reservation.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      415cb800
  4. 26 5月, 2007 1 次提交
    • M
      ocfs2: fix inode leak · 8fccfc82
      Mark Fasheh 提交于
      We weren't cleaning up our inode reference on error in
      ocfs2_reserve_local_alloc_bits(). Add a check for error return and iput() if
      need be. Move the code to set the alloc context inode info to the end of the
      function so we don't have any possibility of passing back a bad pointer.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      8fccfc82
  5. 14 12月, 2006 1 次提交
  6. 02 12月, 2006 7 次提交
  7. 08 8月, 2006 1 次提交
    • M
      ocfs2: allocation hints · 883d4cae
      Mark Fasheh 提交于
      Record the most recently used allocation group on the allocation context, so
      that subsequent allocations can attempt to optimize for contiguousness.
      Local alloc especially should benefit from this as the current chain search
      tends to let it spew across the disk.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      883d4cae
  8. 25 3月, 2006 1 次提交
  9. 10 1月, 2006 1 次提交
  10. 04 1月, 2006 1 次提交