>     The network stack is equally easy to make MP-safe.  In this case we
>     have a shared lock to lookup sockets for host/port combinations and
>     then fine-grained exclusive locks within those sockets.  Route table
>     and other high level operations could in fact remain BGL'd without
>     interfering with the network stack because the network stack *already*
>     caches route table lookups.

        might it be fair to summarize this as: you locks on data
rather than locks on code.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to