1. 18 4月, 2008 2 次提交
  2. 26 1月, 2008 4 次提交
  3. 18 12月, 2007 3 次提交
  4. 13 10月, 2007 2 次提交
  5. 11 7月, 2007 1 次提交
  6. 03 5月, 2007 1 次提交
  7. 27 4月, 2007 5 次提交
  8. 08 12月, 2006 1 次提交
  9. 02 12月, 2006 11 次提交
  10. 22 11月, 2006 1 次提交
  11. 25 9月, 2006 1 次提交
    • 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
  12. 30 6月, 2006 1 次提交
  13. 28 6月, 2006 1 次提交
  14. 27 6月, 2006 1 次提交
  15. 18 5月, 2006 2 次提交
  16. 27 3月, 2006 2 次提交
  17. 25 3月, 2006 1 次提交