* dev_xmit_extended
* tcpv4_rcv_extended
* udpv4_rcv_extended
+You can use the 'ltt-armall' and 'ltt-armnetsync' scripts for this.
+
You also have to make sure there is some TCP traffic between the traced nodes.
++ Viewing traces
be in separate files. This way, adding a new set of modules would require
shipping extra data_structures* files instead of modifying the existing one.
For this to work, Event.type couldn't be an enum, it could be an int and use
-#defines or constants defined the specialized data_structures* files.
+#defines or constants defined in the specialized data_structures* files.
Event.event could be a void*.
++ Stage 2: Event matching
mix) and it will influence the overall behavior of the module.
eg. TCP, UDP, MPI
-matchEvent() takes an Event pointer. An actual matching module doesn't have
-to be able to process every type of event. It has to check that the passed
-event is of a type it can process.
+matchEvent() takes an Event pointer. An actual matching module doesn't have to
+be able to process every type of event. It will only be passed events of a
+type it can process (according to the .canMatch field of its MatchingModule
+struct).
++ Communication between stages 2 and 3: event groups
Communication consists of events grouped in Message, Exchange or Broadcast