1. 18 Apr, 2008 2 commits
  2. 25 Jan, 2008 4 commits
  3. 17 Dec, 2007 3 commits
  4. 12 Oct, 2007 2 commits
  5. 10 Jul, 2007 1 commit
  6. 02 May, 2007 1 commit
  7. 26 Apr, 2007 5 commits
  8. 07 Dec, 2006 1 commit
  9. 01 Dec, 2006 11 commits
  10. 22 Nov, 2006 1 commit
  11. 24 Sep, 2006 1 commit
    • Mark Fasheh's avatar
      ocfs2: Remove i_generation from inode lock names · 24c19ef4
      Mark Fasheh authored
      
      OCFS2 puts inode meta data in the "lock value block" provided by the DLM.
      Typically, i_generation is encoded in the lock name so that a deleted inode
      on and a new one in the same block don't share the same lvb.
      
      Unfortunately, that scheme means that the read in ocfs2_read_locked_inode()
      is potentially thrown away as soon as the meta data lock is taken - we
      cannot encode the lock name without first knowing i_generation, which
      requires a disk read.
      
      This patch encodes i_generation in the inode meta data lvb, and removes the
      value from the inode meta data lock name. This way, the read can be covered
      by a lock, and at the same time we can distinguish between an up to date and
      a stale LVB.
      
      This will help cold-cache stat(2) performance in particular.
      
      Since this patch changes the protocol version, we take the opportunity to do
      a minor re-organization of two of the LVB fields.
      Signed-off-by: default avatarMark Fasheh <mark.fasheh@oracle.com>
      24c19ef4
  12. 29 Jun, 2006 1 commit
  13. 27 Jun, 2006 1 commit
  14. 26 Jun, 2006 1 commit
  15. 17 May, 2006 2 commits
  16. 26 Mar, 2006 2 commits
  17. 24 Mar, 2006 1 commit