1. 15 1月, 2010 2 次提交
  2. 24 12月, 2009 3 次提交
    • S
      ceph: include transaction id in ceph_msg_header (protocol change) · 6df058c0
      Sage Weil 提交于
      Many (most?) message types include a transaction id.  By including it in
      the fixed size header, we always have it available even when we are unable
      to allocate memory for the (larger, variable sized) message body.  This
      will allow us to error out the appropriate request instead of (silently)
      dropping the reply.
      Signed-off-by: NSage Weil <sage@newdream.net>
      6df058c0
    • S
      ceph: control access to page vector for incoming data · 350b1c32
      Sage Weil 提交于
      When we issue an OSD read, we specify a vector of pages that the data is to
      be read into.  The request may be sent multiple times, to multiple OSDs, if
      the osdmap changes, which means we can get more than one reply.
      
      Only read data into the page vector if the reply is coming from the
      OSD we last sent the request to.  Keep track of which connection is using
      the vector by taking a reference.  If another connection was already
      using the vector before and a new reply comes in on the right connection,
      revoke the pages from the other connection.
      Signed-off-by: NSage Weil <sage@newdream.net>
      350b1c32
    • S
      ceph: unregister canceled/timed out osd requests · 529cfcc4
      Sage Weil 提交于
      Canceled or timed out osd requests were getting left in the request list
      and never deallocated (until umount).  Unregister if they are canceled
      (control-c) or time out.
      Signed-off-by: NSage Weil <sage@newdream.net>
      529cfcc4
  3. 22 12月, 2009 3 次提交
  4. 08 12月, 2009 1 次提交
  5. 04 12月, 2009 1 次提交
  6. 02 12月, 2009 1 次提交
  7. 22 11月, 2009 1 次提交
  8. 21 11月, 2009 1 次提交
    • S
      ceph: fix debugfs entry, simplify fsid checks · 0743304d
      Sage Weil 提交于
      We may first learn our fsid from any of the mon, osd, or mds maps
      (whichever the monitor sends first).  Consolidate checks in a single
      helper.  Initialize the client debugfs entry then, since we need the
      fsid (and global_id) for the directory name.
      
      Also remove dead mount code.
      Signed-off-by: NSage Weil <sage@newdream.net>
      0743304d
  9. 19 11月, 2009 3 次提交
  10. 05 11月, 2009 1 次提交
  11. 28 10月, 2009 1 次提交
  12. 16 10月, 2009 1 次提交
  13. 15 10月, 2009 1 次提交
  14. 10 10月, 2009 4 次提交
  15. 07 10月, 2009 1 次提交
    • S
      ceph: OSD client · f24e9980
      Sage Weil 提交于
      The OSD client is responsible for reading and writing data from/to the
      object storage pool.  This includes determining where objects are
      stored in the cluster, and ensuring that requests are retried or
      redirected in the event of a node failure or data migration.
      
      If an OSD does not respond before a timeout expires, keepalive
      messages are sent across the lossless, ordered communications channel
      to ensure that any break in the TCP is discovered.  If the session
      does reset, a reconnection is attempted and affected requests are
      resent (by the message transport layer).
      Signed-off-by: NSage Weil <sage@newdream.net>
      f24e9980