1. 25 9月, 2006 14 次提交
    • 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: Encode i_generation in the meta data lvb · f9e2d82e
      Mark Fasheh 提交于
      When i_generation is removed from the lockname, this will help us determine
      whether a meta data lvb has information that is in sync with the local
      struct inode.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      f9e2d82e
    • M
      ocfs2: Free up some space in the lvb · 4d3b83f7
      Mark Fasheh 提交于
      lvb_version doesn't need to be a whole 32 bits. Make it an 8 bit field to
      free up some space. This should be backwards compatible until we use one of
      the fields, in which case we'd bump the lvb version anyway.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      4d3b83f7
    • 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: manually d_move() during ocfs2_rename() · 1ba9da2f
      Mark Fasheh 提交于
      Make use of FS_RENAME_DOES_D_MOVE to avoid a race condition that can occur
      during ->rename() if we d_move() outside of the parent directory cluster
      locks, and another node discovers the new name (created during the rename)
      and unlinks it. d_move() will unconditionally rehash a dentry - which will
      leave stale data in the system.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      1ba9da2f
    • M
      [PATCH] Allow file systems to manually d_move() inside of ->rename() · 349457cc
      Mark Fasheh 提交于
      Some file systems want to manually d_move() the dentries involved in a
      rename.  We can do this by making use of the FS_ODD_RENAME flag if we just
      have nfs_rename() unconditionally do the d_move().  While there, we rename
      the flag to be more descriptive.
      
      OCFS2 uses this to protect that part of the rename operation with a cluster
      lock.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
      Cc: Al Viro <viro@zeniv.linux.org.uk>
      Cc: Christoph Hellwig <hch@lst.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      349457cc
    • M
      ocfs2: Remove the dentry vote · 1390334b
      Mark Fasheh 提交于
      This is unused now.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      1390334b
    • 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
    • M
      ocfs2: Add dentry tracking API · 80c05846
      Mark Fasheh 提交于
      Replace the dentry vote mechanism with a cluster lock which covers a set
      of dentries. This allows us to force d_delete() only on nodes which actually
      care about an unlink.
      
      Every node that does a ->lookup() gets a read only lock on the dentry, until
      an unlink during which the unlinking node, will request an exclusive lock,
      forcing the other nodes who care about that dentry to d_delete() it. The
      effect is that we retain a very lightweight ->d_revalidate(), and at the
      same time get to make large improvements to the average case performance of
      the ocfs2 unlink and rename operations.
      
      This patch adds the higher level API and the dentry manipulation code.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      80c05846
    • M
      ocfs2: Add new cluster lock type · d680efe9
      Mark Fasheh 提交于
      Replace the dentry vote mechanism with a cluster lock which covers a set
      of dentries. This allows us to force d_delete() only on nodes which actually
      care about an unlink.
      
      Every node that does a ->lookup() gets a read only lock on the dentry, until
      an unlink during which the unlinking node, will request an exclusive lock,
      forcing the other nodes who care about that dentry to d_delete() it. The
      effect is that we retain a very lightweight ->d_revalidate(), and at the
      same time get to make large improvements to the average case performance of
      the ocfs2 unlink and rename operations.
      
      This patch adds the cluster lock type which OCFS2 can attach to
      dentries.  A small number of fs/ocfs2/dcache.c functions are stubbed
      out so that this change can compile.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      d680efe9
    • M
      ocfs2: Update dlmglue for new dlmlock() API · f0681062
      Mark Fasheh 提交于
      File system lock names are very regular right now, so we really only need to
      pass an extra parameter to dlmlock().
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      f0681062
    • M
      ocfs2: Update dlmfs for new dlmlock() API · ea5b3a18
      Mark Fasheh 提交于
      We just need to add a namelen field to the user_lock_res structure, and
      update a few debug prints. Instead of updating all debug prints, I took the
      opportunity to remove a few that are likely unnecessary these days.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      ea5b3a18
    • M
      ocfs2: Allow binary names in the DLM · 3384f3df
      Mark Fasheh 提交于
      The OCFS2 DLM uses strlen() to determine lock name length, which excludes
      the possibility of putting binary values in the name string. Fix this by
      requiring that string length be passed in as a parameter.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      3384f3df
    • M
      ocfs2: Silence dlm error print · e2c73698
      Mark Fasheh 提交于
      An AST can be delivered via the network after a lock has been removed, so no
      need to print an error when we see that.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      e2c73698
  2. 24 9月, 2006 1 次提交
  3. 23 9月, 2006 25 次提交