BIND 10 #2856: memory manager initialization

[BIND 10 Development]

#2856: memory manager initialization
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |  vorner
            Priority:  medium        |                       Status:
           Component:  shmem         |  reviewing
  manager                            |                    Milestone:
            Keywords:                |  Sprint-20130806
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  4             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |  shared memory data source
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => vorner


Comment:

 Do you agree with the following (it's not very clear from the design doc):

 When the memmgr is not in the `READY` state, if it gets notified of a new
 auth subscribing to the readers group, it is fine to assume the new auth
 instance is using the new mapped file and not the old one. For making sure
 there is no race, memmgr should make `SegmentInfo` updates in the main
 thread itself (which also handles communications) and only have the
 builder in a different thread.

 So in such a case, notifications of reader group subscriptions can make
 memmgr add all readers to the current list of readers as they are using
 the latest mapped file.

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