Changeset 603 for trunk/kernel/libk/remote_busylock.h

Timestamp:

Dec 3, 2018, 12:17:35 PM (5 years ago)

Author:

alain

Message:

Improve the FAT32 file system to support cat, rm, cp commands.

File:

• trunk/kernel/libk/remote_busylock.h (modified) (4 diffs)

trunk/kernel/libk/remote_busylock.h

@@ -1 +1 @@
 /*
- * remote_busylock.h: remote kernel busy waiting lock definition.     
+ * remote_busylock.h: remote kernel busy-waiting lock definition.     
  * 
  * Authors  Alain Greiner (2016,2017,2018)
@@ -33 +33 @@
  * This synchronisation object sequencializes all concurrent read or write accesses to a
  * shared object located in any cluster, made by any thread(s) running in any cluster.
- * It uses a busy waiting policy when the tock is taken by another thread, and should
+ * It uses a busy waiting policy when the lock is taken by another thread, and should
  * be used ro execute very short actions, such as basic allocators, or to protect  
  * higher level synchronisation objects, such as remote_queuelock and remote_rwlock.
+ *
  * WARNING: a thread cannot yield when it is owning a busylock (local or remote).
  *
@@ -45 +46 @@
  *   decrements its busylocks counter.
  * 
-:w * - When a thread takes a busylock, it enters a critical section: the busylock_acquire() 
+ * - When a thread takes a busylock, it enters a critical section: the busylock_acquire() 
  *   function disables the IRQs, takes the lock, increments the thread busylocks counter,
- *   and save the SR in lock descriptor and returns.
+ *    save the SR in the lock descriptor and returns.
  *
- * - The busylock_release() function releases the lock, decrements the thread busylock
- *   counter, restores the SR to exit the critical section, and returns
+ * - The busylock_release() function decrements the thread busylock counter,
+ *   restores the SR to exit the critical section, and returns
  *
  * - If a thread owning a busylock (local or remote) tries to deschedule, the scheduler
@@ -58 +59 @@
 /*******************************************************************************************
  * This structure defines a remote_busylock.
- * The <type> and <xlist> fields are used for debug.
- * The type defines the lock usage as detailed in the kernel_config.h file. 
+ * - The <ticket> and <current> fields implement the ticket policy described above.
+ * - The <type> and <xlist> fields are used for debug. The type defines the lock usage,
+ *   as detailed in the kernel_config.h file. 
+ * - The <save_sr> field is used to implement the critical section as decribed above.
  ******************************************************************************************/