Changeset 635 for trunk/kernel/kern/thread.h

Timestamp:

Jun 26, 2019, 11:42:37 AM (5 years ago)

Author:

alain

Message:

This version is a major evolution: The physical memory allocators,
defined in the kmem.c, ppm.c, and kcm.c files have been modified
to support remote accesses. The RPCs that were previously user
to allocate physical memory in a remote cluster have been removed.
This has been done to cure a dead-lock in case of concurrent page-faults.

This version 2.2 has been tested on a (4 clusters / 2 cores per cluster)
TSAR architecture, for both the "sort" and the "fft" applications.

File:

• trunk/kernel/kern/thread.h (modified) (3 diffs)

trunk/kernel/kern/thread.h

@@ -101 +101 @@
 {
         uint32_t     false_pgfault_nr;       /*! number of local page fault               */
+        uint32_t     local_pgfault_nr;       /*! number of local page fault               */
+        uint32_t     global_pgfault_nr;      /*! number of global page fault              */
     uint32_t     false_pgfault_cost;     /*! cumulated cost                           */
-        uint32_t     local_pgfault_nr;       /*! number of local page fault               */
     uint32_t     local_pgfault_cost;     /*! cumulated cost                           */
-        uint32_t     global_pgfault_nr;      /*! number of global page fault              */
     uint32_t     global_pgfault_cost;    /*! cumulated cost                           */
 
@@ -339 +339 @@
  * this. This includes the thread descriptor itself, the associated CPU and FPU context,
  * and the physical memory allocated for an user thread stack.
+ * This function does not remove the thread from the scheduler, as this is done by
+ * the scheduler itself.
  ***************************************************************************************
  * @ thread  : pointer on the thread descriptor to release.
@@ -394 +396 @@
  * The calling thread can run in any cluster, as it uses remote accesses.
  * This function makes a kernel panic if the target thread is the main thread,
- * because * the main thread deletion will cause the process deletion, and a process
+ * because the main thread deletion will cause the process deletion, and a process
  * must be deleted by the parent process, running the wait function.
  * If the target thread is running in "attached" mode, and the <is_forced> argument