BIND 10 #2202: introduce a lock for the data source client in auth

[BIND 10 Development]

#2202: introduce a lock for the data source client in auth
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20121009
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  5
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  background zone loading            |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jinmei


Comment:

 Hello

 Replying to [comment:24 jinmei]:
 > Do compilers really use atomic operations (like xadd) for things like
 > adding a value to integers?  That's against my previous experiences.
 > But even so, I believe we can avoid the use of atomic operations more
 > easily, e.g., by just using a bit more complicated types like double.
 > I'm attaching some experimental diff.  It does not always "fail" but
 > fails sufficiently often in my development environment (more than
 > 80%), and the code is much simpler.

 I don't think they use such thing, but ints, for example, could be atomic
 in
 some architectures by themself.

 I adopted your version (I'm surprised it works, but after checking it, I
 see it
 does). I don't think this will work on single-CPU machine, though.

 > > But the /// ones break the \code snippets :-(. How is it done, then?
 >
 > Really?  How?  From a quick experiment the attached patch worked fine
 > for me.  Maybe it's doxygen version issue?

 For some reason, it gave comment signs before each line of the snipped.
 But
 your version does not. I don't know what I did differently.

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