On 3/9/07, Robert Watson <[EMAIL PROTECTED]> wrote:
It also introduces parallelism in the in-bound network layer processing path by allowing processing to occur in more than one thread at a time. However, you can see
From the experimentation I've done, it seems that for TCP loads at least,
the input path tends to bottleneck on INP_INFO_WLOCK(&tcbinfo), essentially reducing the input path to a single thread. reduced parallelism in some environments as the ithread no longer run
concurrently with the netisr. I would not use net.isr.direct in versions of FreeBSD before 6.1, but it should be pretty safe for 6.1 and later.
Admitedly, the experimentation I've done has been with 6.0, rather than 6.1. Have there been any changes in 6.1 that address the locking in the TCP input path? I'm very interested in being able to run highly parallel TCP loads. Keith _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
