BIND 10 #2088: introduce MemorySegment class

[BIND 10 Development]

#2088: introduce MemorySegment class
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  muks
  jinmei                             |                Status:  assigned
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120717
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  4
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  scalable inmemory                  |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by muks):

 I have added an initial implementation on the branch. These could very
 well not be the implementations we are looking for. From the bug report,
 it's not clear how these methods will be used:

 * Is deallocate() meant to free smaller blocks than what allocate()
 returns?

 * Because these methods will be virtual, a MemorySegment object is
 necessary. Will this be a singleton?

 * Does allMemoryDeallocated() need anything fancy like a set of all
 allocated buffers kept, or is just a counter of total size of memory
 allocated sufficient? (The counter is implemented.)

 Branch trac2088 contains the current implementation.

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