BIND 10 #3124: Move most work to the work thread

BIND 10 Development do-not-reply at isc.org
Wed Aug 28 09:24:33 UTC 2013


#3124: Move most work to the work thread
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  shmem         |  Tasks
  manager                            |                   Resolution:
            Keywords:                |                 CVSS Scoring:
           Sensitive:  0             |              Defect Severity:  N/A
         Sub-Project:  DNS           |  Feature Depending on Ticket:
Estimated Difficulty:  0             |  Simplified memmgr
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Description changed by vorner:

Old description:

> Move all the possible logic into the work thread. The main thread will
> only listen for notifications about need to load zones (#3115),
> configuration updates and new/removed subscribers. It'll simply push the
> notifications and commands to the queue for the work thread (and send ACK
> for the configuration updates, since they are command, not notification),
> but it'll not handle other communication with the readers.
>
> This may simplify the logic in the work thread a bit, but some more will
> come.
>
> Directly handle whatever is needed instead of sending notification about
> completed work and letting the main thread handle it.

New description:

 Move all the possible logic into the work thread. The main thread will
 only listen for notifications about need to load zones (#3115),
 configuration updates and new/removed subscribers. It'll simply push the
 notifications and commands to the queue for the work thread (and send ACK
 for the configuration updates, since they are command, not notification),
 but it'll not handle other communication with the readers.

 This may simplify the logic in the work thread a bit, but some more will
 come.

 Directly handle whatever is needed instead of sending notification about
 completed work and letting the main thread handle it.

 Depends on #3123.

--

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


More information about the bind10-tickets mailing list