|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5 |
|
| #
0a9eefca |
| 09-Mar-2015 |
Matthew Dillon <dillon@apollo.backplane.com> |
dmsg - Stabilization work
* Refactor the circuit failure handling code. When a connection is lost
circuits running through that connection and all sub-circuits/states
(recursively) are aborted.
dmsg - Stabilization work
* Refactor the circuit failure handling code. When a connection is lost
circuits running through that connection and all sub-circuits/states
(recursively) are aborted. This will propagate through the graph and
there are plenty of edge cases where a failure may be propagating in
one direction and a request in the other direction.
The library is responsible for providing missing transaction closures
when circuits and states fail.
* Add code to handle circuit failure races against newly created messages.
The STATE_DYING flag is now inherited by the newly created message from
its parent.
* The state structure on receive is now updated before the callback is
made so it can be atomic with the lock, instead of after.
* Lots of debugging added and some cleanup.
show more ...
|
|
Revision tags: v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc |
|
| #
1b8eded1 |
| 23-Apr-2014 |
Matthew Dillon <dillon@apollo.backplane.com> |
hammer2 - Retool dmsg mechanics to improve virtual circuit design 1/2
* Rip-out the circuit structures and forging code. These changes simplify
the DMSG code considerably.
* Retool the core comm
hammer2 - Retool dmsg mechanics to improve virtual circuit design 1/2
* Rip-out the circuit structures and forging code. These changes simplify
the DMSG code considerably.
* Retool the core command/response messaging mechanics to allow either
side of a transaction to initiate commands and receive responses.
This means we cannot use DMSGF_REPLY to determine whether the transmit-side
or receive-side state RBTREE holds the msgid. Instead we add two more
flags DMSGF_REVTRANS and DMSGF_REVCIRC to tell the receiver which RBTREE
holds the msgid and/or circuit id.
* Retool to allow transaction stacking. Sub-transactions can now run under
their parents.
* Retool the transaction code to provide virtual circuit functionality
through the use of transaction stacking.
With these changes, the normal SPAN mechanism which operates using
open transactions can also be used to route messages over the SPAN.
There is no longer a need to forge a return path because sub-transaction
commands can now be initiated 'out' over an active, received SPAN
transaction.
This part is not completely working yet, it needs the actual routing
code and some adjustments to the SPAN mechanism to prevent path ripups
from interfering with any in-progress transactions. Ultimately the
availability of a new path would have two be detected by the end points
so new 'connections' can be forged over the new, better path.
show more ...
|
| #
01e43224 |
| 19-Apr-2014 |
Matthew Dillon <dillon@apollo.backplane.com> |
libdmsg - refactor remove hammer2-specific code
* Remove hammer2-specific code.
* Refactor the callback API to allow the hammer service code to handle
the H2-specific LNK_CONN commands... mostly
libdmsg - refactor remove hammer2-specific code
* Remove hammer2-specific code.
* Refactor the callback API to allow the hammer service code to handle
the H2-specific LNK_CONN commands... mostly VOLCONF.
show more ...
|
|
Revision tags: v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2 |
|
| #
0d20ec8a |
| 30-Nov-2012 |
Matthew Dillon <dillon@apollo.backplane.com> |
hammer2 - cluster / libdmsg circuit work
* Major work on the virtual circuit code. Note there are still some thread
races.
* Major work on the spanning tree code to allow for future symmetric
hammer2 - cluster / libdmsg circuit work
* Major work on the virtual circuit code. Note there are still some thread
races.
* Major work on the spanning tree code to allow for future symmetric
pathing support.
* fs_label is now part of the RB tree compare, along with pfs_fsid.
(e.g. the serial number for BLK protocol services).
* Rip out the 'router' structure, replace with the 'circuit' structure.
Embed circuit0 in the iocom.
show more ...
|
| #
0c3a8cd0 |
| 25-Oct-2012 |
Matthew Dillon <dillon@apollo.backplane.com> |
hammer2 - Messaging layer separation work part 2
* Move most of the low-level message handling from the hammer2 utility
to a new library called libdmsg.
* Move additional message headers from the
hammer2 - Messaging layer separation work part 2
* Move most of the low-level message handling from the hammer2 utility
to a new library called libdmsg.
* Move additional message headers from the hammer2 vfs code to libdmsg,
cleanup.
* Rename and reorganize a ton of stuff.
show more ...
|