On 3/11/07, Robert Watson <[EMAIL PROTECTED]> wrote:
Yes -- right now the in-bound TCP path is essentially serialized because
of
the tcbinfo lock. The reason for this is that the tcbinfo lock doesn't
just
protect the inpcb chains during lookup, but also effectively acts as a
reference to prevent the inpcb from being freed during input processing.
There are several ways we could start to reduce contention on that lock:
So, why is the tcbinfo lock being used to protect the pcb from deletion?
Why isn't the INP_LOCK on the pcb used, instead?
Keith
--
Well, I didn't find the Holy Grail,
but I did find a rusty cup without too many holes in it...
-- Jeff Semke
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
