| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Since the epoch call callbacks may lock/unlock a mutex the callbacks must be
called from within thread context with thread dispatching enabled. Use thread
pinning to ensure that the calling thread stays on the right processor. Use
the interrupt server to ensure the thread context for the epoch drain.
|
|
|
|
|
| |
Use the PER_CPU_DATA_NEED_INITIALIZATION() macro if necessary to request an
initialization of the per-CPU data.
|
| |
|
|
|
|
|
| |
FreeBSD changed the epoch_enter() and epoch_exit() inline functions into
proper functions after a performance analysis to avoid code bloat.
|
|
|
|
| |
It is a bit more efficient.
|
|
|
|
| |
Close #3749.
|
| |
|
| |
|
|
|
|
|
| |
The _Watchdog_Per_CPU_insert_ticks() assumes that interrupts are
disabled.
|
|
|
|
|
| |
The _Watchdog_Per_CPU_insert_ticks() assumes that interrupts are
disabled.
|
|
|
|
|
|
| |
Git mirror commit 6c2192b1ef8c50788c751f878552526800b1e319.
Update #3472.
|
|
Git mirror commit fb63610a69b0eb7f69a201ba05c4c1a7a2739cf9.
Update #3472.
|