RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2025-02-22 02:27:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

kclient: msgr cleanup

Browse Source
This commit is contained in:
Sage Weil 2009-07-22 11:25:51 -07:00
parent 8d7d3c8a07
commit ea54a6a207
2 changed files with 21 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
src/kernel/messenger.c
View File

@ -11,6 +11,27 @@
#include "super.h"
#include "messenger.h"
/*
* Ceph uses the messenger to exchange ceph_msg messages with other
* hosts in the system. The messenger provides ordered and reliable
* delivery. It tolerates TCP disconnects by reconnecting (with
* exponential backoff) in the case of a fault (disconnection, bad
* crc, protocol error). Acks allow sent messages to be discarded by
* the sender.
*
* The network topology is flat: there is no "client" or "server," and
* any node can initiate a connection (i.e., send messages) to any
* other node. There is a fair bit of complexity to handle the
* "connection race" case where two nodes are simultaneously
* connecting to each other so that the end result is a single
* session.
*
* The messenger can also send messages in "lossy" mode, where there
* is no error recovery or connect retry... the message is just
* dropped if something goes wrong.
*/
/* static tag bytes (protocol control messages) */
static char tag_msg = CEPH_MSGR_TAG_MSG;
static char tag_ack = CEPH_MSGR_TAG_ACK;

19
src/kernel/messenger.h
View File

@ -10,25 +10,6 @@
#include "types.h"
/*
* Ceph uses the messenger to exchange ceph_msg messages with
* other hosts in the system. The messenger provides ordered and
* reliable delivery. It tolerates TCP disconnects by reconnecting
* (with exponential backoff) in the case of a fault (disconnection,
* bad crc, protocol error). Acks allow sent messages to be discarded
* by the sender.
*
* The network topology is flat: there is no "client" or "server," and
* any node can initiate a connection (i.e., send messages) to any other
* node. There is a fair bit of complexity to handle the "connection
* race" case where two nodes are simultaneously connecting to each other
* so that the end result is a single session.
*
* The messenger can also send messages in "lossy" mode, where there is
* no error recovery or connect retry... the message is just dropped if
* something goes wrong.
*/
struct ceph_msg;
#define IPQUADPORT(n) \