On 3/11/07, Robert Watson <[EMAIL PROTECTED]> wrote:
There are several ways we could start to reduce contention on that lock:
(3) Move towards greater granularity of locking for the tcbinfo: instead
of
a single mutex, move to more than one locks, so that different
connections
process
On Wed, 14 Mar 2007, Keith Arner wrote:
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 a
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 preve
On Sun, 11 Mar 2007, Keith Arner wrote:
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 don
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
University of Cambridge
On Thu, 8 Mar 2007, Dave Baukus wrote:
What's the word on netisr_direct ? Do people typically enable this feature ?
Direct dispatch is the default configuration for the network stack in FreeBSD
7.x. Many users have reported performance improvements, especially in hig
On 3/8/07, Dave Baukus <[EMAIL PROTECTED]> wrote:
What's the word on netisr_direct ?
Do people typically enable this feature ?
It really varies with workload. For a small number of streams I get
much better throughput with it enabled for a 10GigE link.
-Kip
___
On Thu, 8 Mar 2007, Dave Baukus wrote:
What's the word on netisr_direct ?
Do people typically enable this feature ?
I always enable it, but have never measured it doing anything useful.
Under light loads, it should reduce network latency and overheads by
a microsecond or two (whatever it takes
