Changes between Version 5 and Version 6 of TLMDT

Timestamp:

May 3, 2011, 12:34:58 PM (14 years ago)

Author:

gioja

Comment:

--

TLMDT

@@ -41 +41 @@
 //Set the transaction as blocking - 2 methods
 extension_ptr->set_blocking();
-extension_ptr->set_blocking_type(BLOCKING);
+extension_ptr->set_blocking_type(BLOCKING); //Default
 
 //Set the transaction as non-blocking - 2 methods
@@ -64 +64 @@
 A VCI Transaction can either be primary or secondary. The VCI transaction is primary only if it is not related to another transaction. That is to say when the response will be caught and treated, no response to another transaction will be sent. A pure Initiator will only send primary transactions while a Target-Initiator will be able to send both.
 
-The Primarity of a transaction is a boolean stored in its payload extension. If primarity is not specified by the user, it is considered as primary.
+The Primarity of a transaction is a boolean stored in its payload extension. If primarity is not specified by the user, it is considered as secondary.
 {{{#!c++
 tlm::tlm_generic_payload *payload_ptr = new tlm::tlm_generic_payload();
@@ -78 +78 @@
 //Set the transaction as secondary - 2 methods
 extension_ptr->set_secondary();
-extension_ptr->set_primarity(false);
+extension_ptr->set_primarity(false); //Default
 
 //Send the transaction the usual way
@@ -128 +128 @@
 
 === 2.2. PDES Null_command
-The Null_command is a message with does not require a response. His only goal is to deliver a temporal information, in order to preserve the synchronization between components. Mostly, the initiator doesn't stop when the null_command message is sent, except if it is waiting for the response from another transaction. This messages allows the different components to respect their time quantums. It is also used to perform the Active_Sync on initiators.
+The Null_command is a message with does not require a response. Its only goal is to deliver a temporal information, in order to preserve the synchronization between components. Mostly, the initiator doesn't stop when the null_command message is sent, except if it is waiting for the response from another transaction. This messages allows the different components to respect their time quantums. It is also used to perform the Active_Sync on initiators. The message scope is local, it cannot be routed or redirected. Receiving a null_command awakes the target if it is waiting. Initiators and interconnects can send Null_commands. 
 {{{#!c++  
 tlm::tlm_generic_payload *payload_ptr = new tlm::tlm_generic_payload();
@@ -148 +148 @@
 
 === 2.3. PDES Null_response
+The Null_response is a message which transits on networks like a VCI responses. Only transactions which are blocking or conditionnaly blocking needs to receive Null_responses. The meaning of this message is : "The response to the associated VCI transaction won't be caught before this time". The Null_response is part of the Active_Sync mechanisms. It is used to predict the future of simulation. The only useful data contained in the Null_response is the temporal information. When an initiator receives a Null_response instead of a VCI response, it allows itself to pursue its treatment, neglecting the need of the VCI response, until the Null_response time. In order to properly aim the right transaction on the right initiator, the VCI transaction is reused for the Null_response. When the Null_response is sent, only the target of this message is awaken. Multiple Null_responses can be sent for a single VCI transaction. Successives Null_response's time related to the same transaction needs to grow.
+
+Interconnects and targets can generate and transmit the Null_responses. Null_responses are useful for preventing deadlocks related to synchronization. For performance optimizations, an interconnect can neglect generating a Null_response when the associated transaction is primary. Since Null_response allows to release parallelism of the simulation, it seems important to send it with the highest time possible.
+{{{#!c++  
+soclib_payload_extension *extension_ptr;
+payload_ptr->get_extension(extension_ptr);
+
+//Set the Null_response flag - 2 methods
+extension_ptr->set_null_response();
+extension_ptr->set_vci_response(false);
+//set the tlm phase
+phase = tlm::BEGIN_RSP;
+//set the local time to transaction time
+time = m_pdes_local_time->get();
+//send a message with command equals to PDES_ACTIVE or PDES_INACTIVE
+p_vci_target->nb_transport_bw(*payload_ptr, phase, time);
+
+//Retrieve information
+extension_ptr->is_null_response();
+extension_ptr->is_vci_response();
+}}}
+
 === 2.4. PDES Sync transaction
 === 2.5. Passive_Sync / Active_Sync