BIND 10 #1752: Measure performance hit of per-message filtering

[BIND 10 Development]

#1752: Measure performance hit of per-message filtering
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  vorner                             |                Status:  closed
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120403
  medium                             |            Resolution:  complete
                  Component:         |             Sensitive:  0
  logging                            |           Sub-Project:  Core
                   Keywords:         |  Estimated Difficulty:  4
            Defect Severity:  N/A    |           Total Hours:  2.81
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by stephen):

 It occurs to me that we could use the format of the message symbol itself
 to implement the filter.  The message symbol is generated by the message
 compiler, and is of the form:
 {{{
 extern const isc::log::MessageID LOG_BAD_DESTINATION =
 "LOG_BAD_DESTINATION"
 }}}
 If we were to make the message symbols writable, it would be possible to
 flag a disabled message by setting it to NULL.  This would speed up the
 test in that it should add only one comparison to the logging path.

 Setting up a map (or other data structure) of message string v address of
 symbol pointing to that string during program start-up would allow the
 location of the symbol and so allow the enabling/disabling of the message
 during program execution.

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