Andes Workshop
http://forum.andestech.com/

coalesable design in Andes NTC/NTM
http://forum.andestech.com/viewtopic.php?f=14&t=969
Page 1 of 1

Author:  jimmy [ Thu Dec 29, 2016 2:37 pm ]
Post subject:  coalesable design in Andes NTC/NTM

explained coalesable meaning in document chapter 2.2.3 of AndeStar_SPA_V3_UM072_V1.4.pdf.

When bufferable device transfer data to bufferable device, both sides write commands will be “UN-ORDERED” transfer. other combination will be "IN-ORDERED" transfer.
Please study following description and tables. You will know.

2.2.3. Address Space Operation Ordering Requirement
In Andes memory architecture, loads and stores to different addresses from an AndesCore™ are, in most part, not ordered except for regions characterized by certain device-related address space attributes. For un-ordered loads and stores, if there is a need to enforce certain ordering between these memory operations, MSYNC instruction must be used to achieve this goal.
The following table lists the address space operation ordering requirement based on the translated address space attributes. The symbols used in this table are defined as:
< : This is a “BEFORE” relation between two operations in time or program sequence. For example, “A < B” in a program means instruction A comes earlier than instruction B in aprogram sequence.
u : This is an “UN-ORDERED” relation between two operations in time of performing their operations.

Attachments:
2016-12-29_132508.png
2016-12-29_132508.png [ 99.43 KiB | Viewed 11922 times ]
2016-12-29_132001.png
2016-12-29_132001.png [ 19.05 KiB | Viewed 11922 times ]

Page 1 of 1 All times are UTC + 8 hours [ DST ]
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
http://www.phpbb.com/