Changes between Version 18 and Version 19 of Projects/GSoC/Atomic_Operations

Timestamp:

05/09/14 15:29:09 (10 years ago)

Author:

André Marques

Comment:

Few text corrections

Projects/GSoC/Atomic_Operations

@@ -117 +117 @@
 
 
-The first part is a directory structure chart, atomic.h is API definition file and cpuatomic.h is implementation file. 
+The first part is a directory structure chart, atomic.h is API definition file and cpuatomic.h is an implementation file. 
 
  |---/cpukit
@@ -142 +142 @@
               |       |                           ----cpu.h
 
-Becuase most of the implementation of atomic operations are assembly instructions, if not they could also be implemented with inlilne C source code. So i place the architecture-independent atomic API definitions to the atomic.h which is visible to other rtems components like score, dirver and etc. The architecture-dependent atomic implementations are placed to the cpuatomic.h which exists in every architecture-related directory as show above. The API is associated with implementations using method like this: 
+Most of the implementation of atomic operations are assembly instructions, if not they could also be implemented with inline C source code. So i place the architecture-independent atomic API definitions to the atomic.h which is visible to other rtems components like score, dirver and etc. The architecture-dependent atomic implementations are placed on the cpuatomic.h which exists in every architecture-related directory as show above. The API is associated with implementations using methods like this: 
 for example, the atomic general load function API: int Atomic_Load_Acq_Int(volatile int *p)
 1. In the implementation file cpuatomic.h it will be implemented like this:
@@ -155 +155 @@
 Synopsis:
 
-The follow is atomic operation API definition in "rtems" style:
+The following is an atomic operation API definition in "rtems" style:
 1. The atomic_store generic functions
    void _Atomic_Store_Rel_<_type_>(volatile _type_ *p, _type_ v);