Browse Source

[2091a] more clarification on the use of separate memsgmt for each zone.

also fixed some text that didn't really make sense.
JINMEI Tatuya 12 years ago
parent
commit
626757dd1e
1 changed files with 5 additions and 3 deletions
  1. 5 3
      src/lib/datasrc/memory_datasrc.cc

+ 5 - 3
src/lib/datasrc/memory_datasrc.cc

@@ -147,9 +147,11 @@ struct ZoneData {
 
 
         // The assert may be too harsh, but we assume we'll discard (rewrite)
         // The assert may be too harsh, but we assume we'll discard (rewrite)
         // this code soon enough.  Until then this would be a good way to
         // this code soon enough.  Until then this would be a good way to
-        // detect any memory leak.  Also, at that point we shouldn't use
-        // a single separate memory segment for each zone tree; normally
-        // zone data for multiple zones will be managed in a single segment.
+        // detect any memory leak.  Also, at that point we should use
+        // a single separate memory segment for each zone tree; eventually
+        // zone data for multiple zones will be managed in a single segment,
+        // at which point the segment will be passed from outside of this
+        // module.
         assert(local_mem_sgmt_.allMemoryDeallocated());
         assert(local_mem_sgmt_.allMemoryDeallocated());
     }
     }