On 3/1/07, Attilio Rao <[EMAIL PROTECTED]> wrote:
Currently, the main problem for this is that somewhere (TM) there mutex gets recursed and recursion is not handled alredy for rwlocks, so kernel starts panicing. Patch for recursion in rwlock is not trivial, but there are ongoing discussions on it.
Well, even if the INP_INFO_[RW]LOCK macros were changed to use shared/exclusive locks rather than a mutex, and the sx locks were fixed to be taken recursively, I'm not sure that would really do the trick for parallelism. In tcp_input(), the code is using INP_INFO_WLOCK(), to take an exclusive lock, so only one thread would be able to be in the TCP input code path anyway. Keith _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, send any mail to "[EMAIL PROTECTED]"
