> > 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. jmb To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: Patchkits: Was :Re: SMP... Brandon D. Valentine
- Re: Patchkits: Was :Re: SMP... Jim Bloom
- Re: Patchkits: Was :Re: SMP... Andrzej Bialecki
- Re: SMP changes and breaking kld obj... Daniel O'Connor
- Re: SMP changes and breaking kl... Andrzej Bialecki
- Re: SMP changes and breakin... Daniel O'Connor
- Re: SMP changes and breakin... David Malone
- Re: SMP changes and breakin... Jesper Skriver
- Re: SMP changes and breaking kld object module compat... Steve Passe
- Re: SMP changes and breaking kld object module c... Matthew Dillon
- Re: SMP changes and breaking kld object modu... Jonathan M. Bresler
- Re: SMP changes and breaking kld object ... Matthew Dillon
- RE: SMP changes and breaking kld object module compat... Alok Dhir
- RE: SMP changes and breaking kld object module compat... Alok Dhir
- Re: SMP changes and breaking kld object module compat... Steve Passe