BIND 10 #2331: design of shared memory / mmap based in-memory data source
BIND 10 Development
do-not-reply at isc.org
Sat Oct 6 03:50:06 UTC 2012
#2331: design of shared memory / mmap based in-memory data source
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: task | Status: new
Priority: medium | Milestone: New
Component: data source | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
We eventually need to support this; otherwise multiple instances of
b10-auth require multiple copies of in-memory image for the same data.
Obviously it doesn't scale with huge size of zones and many instances
of b10-auth running on many-core boxes.
Actually we shouldn't be very far from this goal. The internal data
structures should be fully offset-pointer based, and all memory
allocation/deallocation are encapsulated with an abstraction of
`MemorySegment`, which should be easily adapted to Boost
managed_shared_memory or managed_mapped_file.
We still have to think about several non trivial things:
- overall design of a memory management process (assuming there will
be a new module, tentatively named "b10-memmgr"). how to create and
update memory image in a shared memory region or on a mapped file.
- inter-module protocol between memmgr and others (auth, xfrin,
DDNS, etc)
- maybe configuration
The goal of this ticket is to have discussions on these topics, maybe
led by someone with initial proposals, and (possibly) create specific
development tickets.
--
Ticket URL: <http://bind10.isc.org/ticket/2331>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list