BIND 10 #2856: memory manager initialization

[BIND 10 Development]

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

 * owner:  vorner => muks


Comment:

 Hello

 Replying to [comment:16 muks]:
 > > Same as with unsubscriptions, subscriptions can come at any time IMO.
 > >
 > > But it probably depends on the current state it is in, to which set to
 > > put them and so.
 > >
 > > What is done now?
 >
 > Right now memmgr does not call any of these methods (in `SegmentInfo`)
 > at all. But I don't follow this anymore. What behavior changes are
 > suggested now?

 No, I meant what happens if I call `add_reader` in, lets say,
 SYNCHRONIZING state. Do we throw? If we throw, we should change that (I
 looked and it seems we don't throw, but I better ask if I'm right).

 And, depending on the state, the new reader might need to go to either old
 readers or the current readers (I did not think about when to which, maybe
 putting it to the current ones is OK every time).

 So, depending on the current state, it might be no change is needed. Could
 you go through the states and decide where it makes sense to put them? If
 no change is needed, then it is OK to merge.

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