>Are the conventions for when to use which splfoo() documented in section 9 y=
>et?
>
>        curious,

Perhaps we could fix some of the more egregious errors in those
conventions before documenting them.

For example, using splimp() to lock kernel memory allocation, makes
halfway-accurate profiling of kernel networking code infeasible.

I'd like to see a new `spl' for kernel memory allocation, distinct
from any other `priority level' to better suppport kernel profiling.