1. 11 8月, 2010 1 次提交
  2. 06 8月, 2010 1 次提交
    • S
      ceph: only queue async writeback on cap revocation if there is dirty data · 0eb6cd49
      Sage Weil 提交于
      Normally, if the Fb cap bit is being revoked, we queue an async writeback.
      If there is no dirty data but we still hold the cap, this leaves the
      client sitting around doing nothing until the cap timeouts expire and the
      cap is released on its own (as it would have been without the revocation).
      
      Instead, only queue writeback if the bit is actually used (i.e., we have
      dirty data).  If not, we can reply to the revocation immediately.
      Signed-off-by: NSage Weil <sage@newdream.net>
      0eb6cd49
  3. 04 8月, 2010 3 次提交
  4. 03 8月, 2010 7 次提交
  5. 02 8月, 2010 28 次提交