1. 01 10月, 2006 1 次提交
  2. 25 9月, 2006 3 次提交
    • M
      ocfs2: Remove i_generation from inode lock names · 24c19ef4
      Mark Fasheh 提交于
      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: NMark Fasheh <mark.fasheh@oracle.com>
      24c19ef4
    • M
      ocfs2: Remove special casing for inode creation in ocfs2_dentry_attach_lock() · 0027dd5b
      Mark Fasheh 提交于
      We can't use LKM_LOCAL for new dentry locks because an unlink and subsequent
      re-create of a name/inode pair may result in the lock still being mastered
      somewhere in the cluster.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      0027dd5b
    • M
      ocfs2: Hook rest of the file system into dentry locking API · 379dfe9d
      Mark Fasheh 提交于
      Actually replace the vote calls with the new dentry operations. Make any
      necessary adjustments to get the scheme to work.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      379dfe9d
  3. 21 9月, 2006 3 次提交
  4. 27 3月, 2006 1 次提交
  5. 25 3月, 2006 1 次提交
  6. 04 1月, 2006 1 次提交