Processor Model Example Instance Clause Samples

Processor Model Example Instance. ‌ Figure 5.12 contains an exemplary model at the processor domain, i.e. the internals of a Tile. The model contains two Cores, one RAM and one ROM Memory, a Bus, and a NetworkInterface (NI). All mentioned elements are connected via the Bus. The Ports (black connectors) attached to the Cores and to the NetworkInterface are MasterPorts since they need to be able to initiate communication via the Bus. These MasterPorts are connected to BusMasterInterfaces, and thus, the model elements mentioned above are able to communicate. In contrast, the Memory elements are connected via BusSlavePorts to the BusSlaveInterfaces of the Bus, as these elements do not initiate any communication (passive elements). The left hand side of the NetworkInterface is a model of the gateway to the OnChipNetwork at containing layer (i.e., to the Node layer). The left-most black connector is the OnChipNetworkPort of the Tile that contains the discussed example model. This Port is connected to the NetworkInterface’s OnChipNetworkExport (left connector of NetworkInterface component) that depicts the interface of the processor domain to the on- chip-network. As a result (and also considering the meta-models of the other levels of the DREAMS architecture discussed in the previous sections) the model describes that there is a possible communication route from the two Cores shown in Figure 5.12 to resources in located in other Tiles (via the OnChipNetwork) or Nodes (via OnChipNetworks and OffChipNetworks) . Likewise, the model contains the relevant information to determine routes to the Cores and the Memorys from Figure 5.12 from remote resources. +getPlatformConnectorUnits() : EList<IPlatformConnectorType>+getTransceiverUnits() : EList<Transceiver>+getReceiverUnits() : EList<Receiver>+getTransmitterUnits() : EList<Transmitter> -capacity : EInt org.fortiss.af3.platform «interface» platform::IPlatformPort «interface» platform::IGenericPlatformSourceConnector «interface» platform::IPlatformExport «interface» platform::IPlatformInterface +getPlatformConnectorUnits() : EList<PlatformConnectorUnit> +getTransceiverUnits() : EList<Transceiver> +getReceiverUnits() : EList<Receiver> +getTransmitterUnits() : EList<Transmitter> platform::ExecutionUnit «interface» platform::ICommunicationMaster «interface» platform::IGenericPlatformTargetConnector «interface» platform::ILogicalPlatformArchitectureElement platform::Transceiver «interface» platform::IVirtualizationPlatformArchitectureElement «interface» pla...
View Source

Related to Processor Model Example Instance

  • Software Installation The AGENCY shall request approval in writing from the COUNTY prior to installation of any software on COUNTY computer equipment. All software installations must be supervised by COUNTY technical support staff and proof of licensing is required. Upon completion, the AGENCY is responsible for reconfiguring the computers back to the original state.

  • DATA LOSS The Company does not accept responsibility for the security of Your account or content. You agree that Your use of the Website or Services is at Your own risk.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Recovery Schedule If the initial schedule or any current updates fail to reflect the Work’s actual plan or method of operation, or a contractual milestone date is more than fifteen (15) days behind, Owner may require that a recovery schedule for completion of the remaining Work be submitted. The Recovery Schedule must be submitted within seven (7) calendar days of Owner’s request. The Recovery Schedule shall describe in detail Construction Contractor’s plan to complete the remaining Work by the required Contract milestone date. The Recovery Schedule submitted shall meet the same requirements as the original Construction Schedule. The narrative submitted with the Recovery Schedule should describe in detail all changes that have been made to meet the Contract milestone dates.

  • Cost of Repairs 54.1 Loss or damage to the Works or Materials to be incorporated in the Works between the Start Date and the end of the Defects Correction periods shall be remedied by the Contractor at the Contractor's cost if the loss or damage arises from the Contractor's acts or omissions.