From: Alex Elder <elder@inktank.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: [PATCH 0/9] another batch of messenger patches
Date: Fri, 22 Jun 2012 17:44:04 -0500 [thread overview]
Message-ID: <4FE4F534.1000009@inktank.com> (raw)
Here is another set of small (though not necessarily trivial)
patches to the ceph client messenger code.
They are all the result of recent work that was aimed at making
the messenger code more clearly based on independent states, in
hopes of making the result a bit simpler and more reliable.
Most of these involve making what happens when a connection
reset or closed get handled a bit more completely and/or
consistently.
-Alex
[PATCH 1/9] libceph: encapsulate and document connect sequence
[PATCH 2/9] libceph: encapsulate and document negotiation phase
Each of these moves some blocks of code into their own functions,
and adds a lot of commentary about what's going on during the
connect sequence.
[PATCH 3/9] libceph: close the connection's socket on reset
Resetting a connection clears all connection state, but never
actually closes the socket. Now it will.
[PATCH 4/9] libceph: don't close socket in OPENING state
This removes the unnecessary call to con_close_socket() when
a socket is found to be in OPENING state.
[PATCH 5/9] libceph: change TAG_CLOSE handling
[PATCH 6/9] libceph: kill fail_protocol()
These let the normal fault handling code take care of the receipt
of a CLOSE tag from the peer, or of one of the other tags that
can be sent to indicate a connection problem.
[PATCH 7/9] libceph: close connection on reset tag
This causes a more complete reset to occur when a RESETSESSION
tag is received.
[PATCH 8/9] libceph: close connection on connect failure
This removes the unnecessary call to con_close_socket() when
a socket is found to be in CLOSED state. (Probably should
have been moved up next to patch 4/9, above.)
[PATCH 9/9] libceph: set CONNECTING state even earlier
This sets the state of a connection to CONNECTING earlier
than it was occurring before.
next reply other threads:[~2012-06-22 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 22:44 Alex Elder [this message]
2012-06-22 22:48 ` [PATCH 1/9] libceph: encapsulate and document connect sequence Alex Elder
2012-06-22 22:48 ` [PATCH 2/9] libceph: encapsulate and document negotiation phase Alex Elder
2012-06-22 22:48 ` [PATCH 3/9] libceph: close the connection's socket on reset Alex Elder
2012-06-22 22:48 ` [PATCH 4/9] libceph: don't close socket in OPENING state Alex Elder
2012-06-22 22:48 ` [PATCH 5/9] libceph: change TAG_CLOSE handling Alex Elder
2012-06-22 22:48 ` [PATCH 6/9] libceph: kill fail_protocol() Alex Elder
2012-06-22 22:48 ` [PATCH 7/9] libceph: close connection on reset tag Alex Elder
2012-06-22 22:48 ` [PATCH 8/9] libceph: close connection on connect failure Alex Elder
2012-06-22 22:49 ` [PATCH 9/9] libceph: set CONNECTING state even earlier Alex Elder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE4F534.1000009@inktank.com \
--to=elder@inktank.com \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.