Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 May 2004 11:32:08 -0700
From:      Luigi Rizzo <rizzo@icir.org>
To:        Matthew Dillon <dillon@apollo.backplane.com>
Cc:        Robert Watson <rwatson@freebsd.org>
Subject:   Re: Network Stack Locking
Message-ID:  <20040525113208.A74130@xorpc.icir.org>
In-Reply-To: <200405251820.i4PIKnil093871@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, May 25, 2004 at 11:20:49AM -0700
References:  <Pine.NEB.3.96L.1040524234219.98946L-100000@fledge.watson.org> <200405251820.i4PIKnil093871@apollo.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 25, 2004 at 11:20:49AM -0700, Matthew Dillon wrote:
...
> :Actually, this was the specific point I was making also :-).  The question
> :I was asking was about the depth of the message queues between protocol
> :stack layers in actual measurements -- are you observing substantial
> :coallescing between layers as a result of the queues at this point?  I'm
...
>     It should also be noted that since today's processors are so damn fast,
>     actually maxing out the cpu before maxing out the PCI bus(es), at least
>     on a standard workstation, is difficult.

that's where the soekris comes handy :)
(yes i understand that much of the issues here are related to SMP,
but there lot of evidence that a non-smp 5.x kernel is significantly
slower than the equivalent 4.x code, even on heavy network i/o
loads, so there is certainly something to clean up there too).

cheers
luigi



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040525113208.A74130>