>> spl is for blocking interrupts. Process-related things shouldn't be and >> mostly aren't touched by interrupts.
>But without an spl, couldn't multiple processes do Very Bad Things in a >partially shared proc context? They can do that with or without an spl if they don't lock things properly spl can give improper giant locking as a side effect, but it doesn't necessarily prevent other processes running, since tsleep() isn't locked by spls. Bruce To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
