1. 19 10月, 2010 1 次提交
    • C
      xfs: remove the ->kill_root btree operation · c0e59e1a
      Christoph Hellwig 提交于
      The implementation os ->kill_root only differ by either simply
      zeroing out the now unused buffer in the btree cursor in the inode
      allocation btree or using xfs_btree_setbuf in the allocation btree.
      
      Initially both of them used xfs_btree_setbuf, but the use in the
      ialloc btree was removed early on because it interacted badly with
      xfs_trans_binval.
      
      In addition to zeroing out the buffer in the cursor xfs_btree_setbuf
      updates the bc_ra array in the btree cursor, and calls
      xfs_trans_brelse on the buffer previous occupying the slot.
      
      The bc_ra update should be done for the alloc btree updated too,
      although the lack of it does not cause serious problems.  The
      xfs_trans_brelse call on the other hand is effectively a no-op in
      the end - it keeps decrementing the bli_recur refcount until it hits
      zero, and then just skips out because the buffer will always be
      dirty at this point.  So removing it for the allocation btree is
      just fine.
      
      So unify the code and move it to xfs_btree.c.  While we're at it
      also replace the call to xfs_btree_setbuf with a NULL bp argument in
      xfs_btree_del_cursor with a direct call to xfs_trans_brelse given
      that the cursor is beeing freed just after this and the state
      updates are superflous.  After this xfs_btree_setbuf is only used
      with a non-NULL bp argument and can thus be simplified.
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAlex Elder <aelder@sgi.com>
      c0e59e1a
  2. 01 9月, 2009 1 次提交
  3. 02 7月, 2009 1 次提交
  4. 29 3月, 2009 1 次提交
  5. 30 10月, 2008 32 次提交
  6. 13 8月, 2008 1 次提交
  7. 07 2月, 2008 1 次提交
  8. 14 7月, 2007 1 次提交
  9. 10 2月, 2007 1 次提交
    • E
      [XFS] Remove unused arguments from the XFS_BTREE_*_ADDR macros. · 2c36dded
      Eric Sandeen 提交于
      It makes it incrementally clearer to read the code when the top of a macro
      spaghetti-pile only receives the 3 arguments it uses, rather than 2 extra
      ones which are not used. Also when you start pulling this thread out of
      the sweater (i.e. remove unused args from XFS_BTREE_*_ADDR), a couple
      other third arms etc fall off too. If they're not used in the macro, then
      they sometimes don't need to be passed to the function calling the macro
      either, etc....
      
      Patch provided by Eric Sandeen (sandeen@sandeen.net).
      
      SGI-PV: 960197
      SGI-Modid: xfs-linux-melb:xfs-kern:28037a
      Signed-off-by: NEric Sandeen <sandeen@sandeen.net>
      Signed-off-by: NDavid Chinner <dgc@sgi.com>
      Signed-off-by: NTim Shimmin <tes@sgi.com>
      2c36dded