BIND 10 #2856: memory manager initialization

[BIND 10 Development]

#2856: memory manager initialization
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |              Keywords:
                  Component:  shmem  |             Sensitive:  0
  manager                            |           Sub-Project:  DNS
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  shared memory data source          |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 Subtask of #2830.  Depend on #2854 and #2855.

 On top of the minimal framework (#2854), extend memmgr so that it will
 actually create two copies of mapped file for all "mapped" type of
 segments in the `SegmentInfo` list.

 It would look like:

 {{{
 for datasrc in datasrces:
     if datasrc.segment_type != "mapped":
         continue
     client_list.reset_memory_segment(datasrc.datasrc_name, "CREATE",
                                      {"mapped-file": datasrc.map_file_base
 +
                                       str(datasrc.current_file_id)})
     for zone_name in datasrc.cached_zones:
         writer = client_list.get_cache_zone_writer(zone_name)
         writer.load()
         writer.install()
         writer.cleanup()
 }}}

 We could repeat the same procedure for the copy version, or we could
 simply copy the file (which would be much faster).

-- 
Ticket URL: <http://bind10.isc.org/ticket/2856>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development