Changeset 657 for trunk/kernel/mm/vmm.h

Timestamp:

Mar 18, 2020, 11:16:59 PM (4 years ago)

Author:

alain

Message:

Introduce remote_buf.c/.h & socket.c/.h files.
Update dev_nic.c/.h files.

File:

• trunk/kernel/mm/vmm.h (modified) (7 diffs)

trunk/kernel/mm/vmm.h

@@ -3 +3 @@
  *
  * Authors   Ghassan Almaless (2008,2009,2010,2011, 2012)
- *           Mohamed Lamine Karaoui (2015)
- *           Alain Greiner (2016,2017,2018,2019)
+ *           Alain Greiner (2016,2017,2018,2019,2020))
  *
  * Copyright (c) UPMC Sorbonne Universites
@@ -31 +30 @@
 #include <list.h>
 #include <queuelock.h>
+#include <remote_queuelock.h>
 #include <hal_gpt.h>
 #include <vseg.h>
@@ -208 +208 @@
 
 /*********************************************************************************************
- * This function modifies the size of the vseg identified by <process> and <base> arguments
- * in all clusters containing a VSL copy, as defined by <new_base> and <new_size> arguments.
- * This function is called by the sys_munmap() function, and can be called by a thread
- * running in any cluster, as it uses remote accesses.
+ * This function modifies the vseg identified by <process> and <base> arguments in all
+ * clusters containing a VSL copy, as defined by <new_base> and <new_size> arguments.
+ * The new vseg, defined by the <new_base> and <new_size> arguments must be included
+ * in the existing vseg. The target VSL size and base fields are modified in the VSL.
+ * This is done in all clusters containing a VMM copy to maintain VMM coherence. 
+ * It is called by the sys_munmap() and dev_fbf_resize_window() functions.
+ * It can be called by a thread running in any cluster, as it uses the vmm_resize_vseg() in
+ * the local cluster, and parallel RPC_VMM_RESIZE_VSEG for remote clusters.
  * It cannot fail, as only vseg registered  in VSL copies are updated.
  *********************************************************************************************
@@ -228 +232 @@
  * the VSL and remove all associated PTE entries from the GPT.
  * This is done in all clusters containing a VMM copy to maintain VMM coherence. 
- * This function can be called by a thread running in any cluster, as it uses the
- * vmm_remove_vseg() in the local cluster, and the RPC_VMM_REMOVE_VSEG for remote clusters.
+ * It is called by the sys_munmap() and dev_fbf_resize_window() functions.
+ * It can be called by a thread running in any cluster, as it uses the vmm_remove_vseg() in
+ * the local cluster, and parallel RPC_VMM_REMOVE_VSEG for remote clusters.
  * It cannot fail, as only vseg registered  in VSL copies are deleted.
  *********************************************************************************************
@@ -317 +322 @@
  * It must be called by a local thread, running in the cluster containing the modified VMM.
  * Use the RPC_VMM_REMOVE_VSEG if required.
- * It makes a kernel panic if the process is not registered in the local cluster,
- * or if the vseg is not registered in the process VSL.
+ * It makes a kernel panic if the process is not registered in the local cluster.
  * For all vseg types, the vseg is detached from local VSL, and all associated PTEs are
  * unmapped from local GPT. Other actions depend on the vseg type:
@@ -340 +344 @@
 /*********************************************************************************************
  * This function resize a local vseg identified by the <process> and <vseg> arguments.
- * It is called by the vmm_global_resize() function.
- * It must be called by a local thread, running in the cluster containing the modified VMM.
+ * Both the "size" and "base" fields are modified in the process VSL. When the new vseg
+ * contains less pages than the target vseg, the relevant pages are removed from the GPT. 
+ * It is called by the vmm_global_resize() and dev_fbf_resize_window() functions.
+ * It must be called by a local thread, running in the cluster containing the modified VSL.
  * Use the RPC_VMM_RESIZE_VSEG if required.
- * It makes a kernel panic if the process is not registered in the local cluster,
- * or if the vseg is not registered in the process VSL.
- * The new vseg, defined by the <new_base> and <new_size> arguments must be strictly
- * included in the target vseg. The target VSL size and base fields are modified in the VSL.
- * If the new vseg contains less pages than the target vseg, the relevant pages are
- * removed from the GPT. 
  * The VSL lock protecting the VSL must be taken by the caller.
  *********************************************************************************************
@@ -454 +454 @@
                          ppn_t  * ppn );
 
-
 #endif /* _VMM_H_ */