| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This can lead to better cache utilization down the common paths where we don't
touch the link.
|
| |
|
|
|
|
|
| |
Previously, we made the user deal with this themselves, but that's not good
enough; if hooks may allocate, we should test the allocation pathways down
hooks. If we're doing that, we might as well actually implement the protection
for the user.
|
| |
|
|
|
| |
When we run out of space in which to store hooks, we should return EAGAIN from
the mallctl, but not otherwise misbehave.
|
| |
|
|
|
| |
This simplifies the mallctl call to install a hook, which should only take a
single argument.
|
| | |
|
|
|
The hook module allows a low-reader-overhead way of finding hooks to invoke and
calling them.
For now, none of the allocation pathways are tied into the hooks; this will come
later.
|
