Changes between Version 17 and Version 18 of CacheCoherence
- Timestamp:
- Dec 18, 2012, 11:15:50 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CacheCoherence
v17 v18 59 59 the target is a memory cache controller, acting as a physical memory bank, or another VCI target peripheral. This target can be located in any cluster. 60 60 61 The L1 cache controller can issue several simultaneous VCI transactions, that must be distinguished by the VCI TRDID field value. The VCI PKTID field is not used.61 The L1 cache controller can issue several simultaneous VCI transactions, that must be distinguished by the VCI TRDID field value. The VCI PKTID field is also used to distinguish transaction types. 62 62 63 * A '''READ''' transaction can be a single word request (in case of uncached access), or a burst, corresponding to a complete cache line (16 words). A READ burst transaction initiated by any DMA controller must respect the same 16 words cache line format. For all READ transaction, the VCI command packet contains one single VCI flit. The VCI CMD field contains the VCI_READ code. The VCI PLEN field is used to define the burst length (number of bytes). A READ transaction has a type, encoded in the t wo LSB bits of the VCI PKTID field, and the the MSB bit must be 0.63 * A '''READ''' transaction can be a single word request (in case of uncached access), or a burst, corresponding to a complete cache line (16 words). A READ burst transaction initiated by any DMA controller must respect the same 16 words cache line format. For all READ transaction, the VCI command packet contains one single VCI flit. The VCI CMD field contains the VCI_READ code. The VCI PLEN field is used to define the burst length (number of bytes). A READ transaction has a type, encoded in the three LSB bits of the VCI PKTID field (the MSB bit is ignored). 64 64 65 || TRDID for Uncached Data ||0...00||66 || TRDID for Cached Data ||0...01||67 || TRDID for Uncached Instruction ||0...10||68 || TRDID for Cached Instruction ||0...11||65 || PKTID for Uncached Data ||X000|| 66 || PKTID for Cached Data ||X001|| 67 || PKTID for Uncached Instruction ||X010|| 68 || PKTID for Cached Instruction ||X011|| 69 69 70 * A '''WRITE''' transaction can be a single word request or a variable length burst request. In case of burst, the VCI command packet contains at most 8 VCI flits, with consecutive addresses. All words belong to the same half cache line, and the VCI BE field can have different values for each flit (including the zero value). The VCI response packet contains one VCI flit. A WRITE burst transaction initiated by any DMA controller must respect the same 8 aligned words constraint. The VCI CMD field contains the VCI_WRITE code. The MSB bit of the TRDID field must be 1. The other bits in the TRDID field areused to code the slot index in the write buffer. If the modified cache line is replicated in one or several other L1 caches, the memory cache must guaranty that all copies have been updated or invalidated before the WRITE transaction is acknowledged.70 * A '''WRITE''' transaction can be a single word request or a variable length burst request. In case of burst, the VCI command packet contains at most 8 VCI flits, with consecutive addresses. All words belong to the same half cache line, and the VCI BE field can have different values for each flit (including the zero value). The VCI response packet contains one VCI flit. A WRITE burst transaction initiated by any DMA controller must respect the same 8 aligned words constraint. The VCI CMD field contains the VCI_WRITE code. The PKTID field contains the TYPE_WRITE code (X100, MSB bit is ignored). The TRDID field is used to code the slot index in the write buffer. If the modified cache line is replicated in one or several other L1 caches, the memory cache must guaranty that all copies have been updated or invalidated before the WRITE transaction is acknowledged. 71 71 72 || TRDID for Write burst ||1 wbuf_index|| 72 || TRDID for Write burst ||wbuf_index|| 73 || PKTID for Write burst || X100|| 73 74 74 75 * The TSAR architecture supports the '''LL/SC''' mechanism for atomic operations (see AtomicOperations). … … 114 115 115 116 116