Gleb Smirnoff
b79aa45e0e
For compatibility KPI functions like if_addr_rlock() that used to have ...
mutexes but now are converted to epoch(9) use thread-private epoch_tracker.
Embedding tracker into ifnet(9) or ifnet derived structures creates a non
reentrable function, that will fail miserably if called simultaneously from
two different contexts.
A thread private tracker will provide a single tracker that would allow to
call these functions safely. It doesn't allow nested call, but this is not
expected from compatibility KPIs.
Reviewed by: markj
2018-11-13 22:58:38 +00:00
2018-11-12 21:01:28 +00:00
2018-11-09 19:16:01 +00:00
2018-11-07 18:28:55 +00:00
2018-11-05 18:47:29 +00:00
2018-11-10 01:58:37 +00:00
2018-11-09 21:02:07 +00:00
2018-11-12 17:10:44 +00:00
2018-11-13 20:07:55 +00:00
2018-10-26 20:53:01 +00:00
2018-10-20 20:45:49 +00:00
2018-11-13 22:41:20 +00:00
2018-11-12 22:18:11 +00:00
2018-11-06 22:50:50 +00:00
2018-11-07 16:28:09 +00:00
2018-11-10 21:02:32 +00:00
2018-11-12 21:01:28 +00:00
2018-09-26 17:12:14 +00:00
2018-11-13 22:58:38 +00:00
2018-07-18 00:56:25 +00:00
2018-10-20 22:39:35 +00:00
2018-11-05 21:34:17 +00:00
2018-11-01 23:11:47 +00:00
2018-11-13 22:58:38 +00:00
2018-08-10 20:37:32 +00:00
2018-11-04 19:10:44 +00:00
2018-11-10 03:00:36 +00:00
2018-11-12 11:20:59 +00:00
2018-10-21 14:19:16 +00:00
2018-11-12 11:20:59 +00:00
2018-07-30 15:46:40 +00:00
2018-06-16 08:26:23 +00:00
2018-09-09 07:20:15 +00:00
2018-10-23 18:07:37 +00:00
2018-11-13 09:19:07 +00:00
2018-11-13 18:20:27 +00:00
2018-07-20 12:03:16 +00:00
2018-11-02 20:50:22 +00:00
2018-11-05 21:34:17 +00:00
2018-11-13 22:58:38 +00:00
2018-10-21 08:29:36 +00:00
2018-07-15 00:31:17 +00:00
2018-11-09 18:56:40 +00:00
2018-11-13 21:40:56 +00:00
2018-11-13 19:44:40 +00:00
2018-11-12 19:17:26 +00:00
2018-09-13 07:14:11 +00:00
b79aa45e0e