>I was mostly trying to push the locks down so that they weren't held during
>attach and remove. I was using them to protect mostly the kthread state flag
>in the softc, as well as other variables in the softc.
It seems to me that having a single thread per-softc gives you this
protection without requiring any locks. Other than having to aquire
Giant at thread starup (as most code below us is not thread safe yet),
I don't see any other locking requirements.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message