Processor Modules

Figure 158: Standard Icon Used for a Processor Module

Standard icon for a processor module

Processor modules are the primary general-purpose building blocks of node models. Their behavior can be completely specified by setting their “process model” attribute, which specifies the process model to be executed by the module. This process model can respond to external events or interrupts as desired to model a specific function. Processors can be connected to other modules to send and receive packets via any number of packet streams. For example, a module designed to multiplex a number of data channels over a communications link might have several input packet streams and one output packet stream.

Processor modules are used to do general processing of data packets. A typical processor might receive a packet on an input stream, do some processing, and send the packet out again on an output stream. The output packet might be delayed for a short time, or it might be modified with respect to the input packet. For example, a common use of processors is in modeling a layered protocol stack, where each layer provides a well-defined service to the adjacent layer through a specific interface. In this case, a separate processor module is typically used to model each layer of the protocol, exchanging packets of data with the modules that represent the next higher and lower layers.

Processor modules can act as traffic generators when you specify the correct process model for the module’s “model” attribute. When you specify such a model, attributes that configure traffic (interarrival times, packet size, probability density functions) are promoted and appear in the processor module’s attribute list. The standard model set includes process models implemented as traffic generators for several traffic types, including bursty traffic and self-similar traffic.

While processor modules are often connected to other modules via pairs of streams (input streams and output streams), this is not always the case. For instance, it is possible to use a processor module as a “controller” within a node model. In such cases, the processor often communicates directly with other modules through statistic wires or remote interrupts. In fact, it might not use any packet streams at all. Processor modules can also be used as traffic sources (generators) or sinks, in which case they might have only output streams or only input streams.

Node models may employ both processor modules and queue modules (described in the next section) to implement general processing of packets. Normally, a processor module would be used in cases where a packet can be completely processed in response to the interrupt associated with its arrival or generation. If this is not the case, and it is necessary to buffer the packet while awaiting a later event to complete processing, then a queue module, with its additional buffering resources, is likely to be more correct. This is particularly true if multiple packets must be buffered simultaneously.

Like all objects, processors have a number of built-in attributes that configure their behavior. These attributes can be specified in the node domain, typically using the graphical user interface of the Node Editor. However, processors are one of the special objects that support a “model” attribute, in this case to select the processor’s root process model. When selecting a process model, a processor’s attributes may change: new attributes may appear, existing attributes may change values, and certain attributes may disappear. This depends on the process model’s declared model attributes and on its attribute interfaces. Process model attribute interfaces allow the process model developer to specify values in advance for processor built-in attributes. At the same time, a processor attribute can be given a status of hidden which means that it will exist and have a specified value, but will not appear on the processor’s attribute list in the user interface. The process model’s model attributes allow new attributes to be invented and to automatically be appended to be inherited by the processor object.

For additional information, see: