Changes between Version 2 and Version 3 of TLMDT

Timestamp:

May 2, 2011, 6:38:24 PM (14 years ago)

Author:

gioja

Comment:

--

TLMDT

@@ -1 @@
-== TLMDT Modeling for tightly interdependent architectures with several levels of interconnections ==
-=== 0. Introduction
+= TLMDT Modeling for tightly interdependent architectures with several levels of interconnections =
+== 0. Introduction
 ''This document is still under development''.
 
@@ -20 +20 @@
 * Components which are target and initiator at the same time.
 
-=== 1. VCI Messages usage
-=== 2. PDES Messages usage
-=== 3. Efficient time modeling in a multi-transactionnal VCI Component
-=== 4. VCI Initiator modeling
-=== 5. VCI Target-Initiator (decoupled) modeling
-=== 6. VCI Target-Initiator (coupled) modeling
-=== 7. VCI Target modeling
-=== 8. VCI Local Crossbar modeling
-=== 9. VCI Global Crossbar modeling
-=== 10. Proof of the deadlock free feature
-=== 11. Locating the loss in precision
+== 1. VCI Transactions
+The VCI Transactions representation mostly remains the same. Two new concepts are introduced for optimization and performance gain. They both got default value which will allow to skip this aspect for convenience. However, this will, in some cases, increase the part of PDES communication (compared to the VCI one) and slow down the simulation.
+=== 1.1. Blocking type
+=== 1.2. Primarity
+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 no primarity is specified by the user, it is considered as primary.
+{{{#!c++
+tlm::tlm_generic_payload *payload_ptr = new tlm::tlm_generic_payload();
+soclib_payload_extension *extension_ptr = new soclib_payload_extension();
+
+//Fill the transaction with the necessary datas
+...
+
+//Set the transaction as primary - 2 methods
+extension_ptr->set_primary();
+extension_ptr->set_primarity(true);
+
+//Set the transaction as secondary - 2 methods
+extension_ptr->set_secondary();
+extension_ptr->set_primarity(false);
+
+//Send the transaction the usual way
+...
+}}}
+== 2. PDES Messages
+=== 2.1. PDES Activity message
+The PDES activity message remains unmodified. The activity message intends to connect or disconnect an initiator from the interconnect with which it is linked. If the activity of an initiator is true, then the associated centralized buffer slot on the interconnect will be handled for the temporal arbitration, otherwise it won't. The following code is a recall from the linked TLMDT for SOCLIB specification.
+{{{#!c++
+send to interconnect the initiator activity status
+void my_initiator::sendActivity()
+{
+  tlm::tlm_generic_payload *payload_ptr = new tlm::tlm_generic_payload();
+  soclib_payload_extension *extension_ptr = new soclib_payload_extension();
+  tlm::tlm_phase            phase;
+  sc_core::sc_time          time;
+
+  // set the active or inactive command
+  if(m_pdes_activity_status->get()) extension_ptr->set_active();
+  else extension_ptr->set_inactive();
+  // set the extension to tlm payload
+  payload_ptr->set_extension (extension_ptr);
+  //set the tlm phase
+  phase = tlm::BEGIN_REQ;
+  //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_init->nb_transport_fw(*payload_ptr, phase, time);
+  //wait a response
+  wait(m_rspEvent);
+}
+}}}
+Usage :
+{{{#!c++
+  //active the initiator and inform to interconnect
+  m_pdes_activity_status->set(true);
+  sendActivity();
+}}}
+
+{{{#!c++
+  //desactive the initiator and inform to interconnect
+  m_pdes_activity_status->set(false);
+  sendActivity();
+}}}
+
+=== 2.2. PDES Null_command
+=== 2.3. PDES Null_response
+=== 2.4. PDES Sync transaction
+
+== 3. Efficient time modeling in a multi-transactionnal VCI Component
+== 4. VCI Initiator modeling
+== 5. VCI Target-Initiator (decoupled) modeling
+== 6. VCI Target-Initiator (coupled) modeling
+== 7. VCI Target modeling
+== 8. VCI Local Crossbar modeling
+== 9. VCI Global Crossbar modeling
+== 10. Proof of the deadlock free feature
+== 11. Locating the loss in precision