flok 0.0.81 → 0.0.82

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 34171632263d52984e5054c52cbe49a8a211a128
-  data.tar.gz: 864c32e073e18f76e714883b098c5fe8115b1cb7
+  metadata.gz: ebf963c82063ec89074d43114c4416bcc3505df8
+  data.tar.gz: ece62f398cf5e92ce976597f1fee070678bf13d4
 SHA512:
-  metadata.gz: 572ef58be4f5556a8627ebbbf9bbb5fd8e8088a435ef114bb539befd061f9790e6f39e9dc1b05134a79ed155a681c8688fe2570b45d3517cc8cbfa0f0847bf96
-  data.tar.gz: 479b11b9c06d97ca855c00813aaf7b5eaafa646df33b115df3e19d644c0ef90551bc59d7c6c1fdaf71ce23ce5b86c69963e5f93d2301ff2d4de513f17465a2ec
+  metadata.gz: 5b3367ebb243879208147f3b944558fb880e9774c00338e390b0d947cc41ca088a1638ca3db3915deab288bc2477b7955ad39a8095e66ce4942c71f54a2a98e1
+  data.tar.gz: e85b5607da669fcac1a3e795541ca7b37cf9f59295c187989bd367b2db26d2701dfcf69b28bbc22c82ffad4114d5e87c95f6ec552da50c5b48f489d7e66a9841

data/docs/services/vm.md

@@ -171,15 +171,24 @@ The pager synchronization daemon is embodied in the function called `vm_pg_sync_
       during a sync call for disk reads or the synchronous `read_sync` request. The format for each element in the array is `{"page_id": [bp1, bp2], ...}`
   * `vm_pager_waiting_read` - A hash that maps `[ns][page_id]` into a hash that represents a the page that was trying to be written.
       needed to be read before notifying the pager. Multiple write attempts on the same page before the disk response will undefined behavior.
-  * `vm_unsynced_*`
-    * `vm_unsynced` - A hash that maps `vm_unsynced_fresh[ns][page_id]` to an integer that is either `0` or `1`. the vm sync daemon reads over this
+  * `vm_unsynced`
+    * `vm_unsynced` - A hash that maps `vm_unsynced[ns][page._id]` to an integer that is either `0` or `1`. the vm sync daemon reads over this
         queue and `0` means that it was just requested via `vm_pg_mark_needs_sync` and needs to be incremented to `1`. `1` means that the vm sync
         daemon must contact the pager for the `sync` action. This will happend until the pager calls `vm_pg_unmark_needs_sync` which will remove it
-        from this hash
+        from this hash.
+    * `vm_unsynced_is_dirty` - A boolean value that indicates whether the `vm_unsynced` needs to be paged-out to disk.
+    * `vm_unsynced_paged_in` - A boolean that indicates whether the `vm_unsynced` needs to be paged in from disk (used once on wakeup)
 
 ##Helper Methods
 
 ###Functional
+####Periodically called (daemons)
+  * `vm_pg_sync_wakeup` - for all pages in `vm_unsynced`, the pagers are notified of a `sync` request
+  * `vm_pg_sync_pagein` - If has not happend yet, the `vm_unsynced` table is loaded from disk via the the special namespace `__reserved__` and key
+      `vm_unsynced`
+  * `vm_pg_sync_pageout` - If the `vm_unsynced_is_dirty` is set, the `vm_unsynced` is written out to special namespace `__reserved__` and key
+      `vm_unsynced`
+
 ####Page modification (assuming inputs are modifiable)
   * **Generic Page**
     * `vm_create_page(id)` - **this does not write anything to memory. It has no side effects except returning a hash**.

data/lib/flok/version.rb

@@ -1,3 +1,3 @@
 module Flok
-  VERSION = "0.0.81"
+  VERSION = "0.0.82"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: flok
 version: !ruby/object:Gem::Version
-  version: 0.0.81
+  version: 0.0.82
 platform: ruby
 authors:
 - seo
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-08-05 00:00:00.000000000 Z
+date: 2015-08-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: execjs