freebsd router

[Matthew D. Fuller]

On Wed, Jan 11, 2006 at 06:41:37AM -0800 I heard the voice of
Danial Thom, and lo! it spake thus:
> 
> No, that's wrong. Firstly, you CAN do things in parallel, but when
> you chop up the "tasks" in routing you don't gain anything, in fact
> you lose, because it is best done as a single task.

No, because you can route MULTIPLE PACKETS AT ONE TIME.  Only the most
trivial and uninteresting routing tasks move packets one at a time
from one interface to another.  Why should my packet coming in em1 and
going out em3 have to wait until you're done with your packet coming
in em0 and going out em2?  MP is a distinct advantage.


> I can promise you that 7.0 is far from "probably" anything. They are
> a long way off. Maybe come up with some real benchmarks (like the
> one I suggested in my other post) so you won't be bamboozled by the
> hype so easily.

Ooh, darn!  All that hype bamboozled its way sideways into my tear
ducts, and now I can't see straight!  Or maybe it's just 'cuz I
actually read -net and -cvs...

    This work has been shown to increase fast-forwarding from ~570
    kpps to ~750 kpps (note that the same NIC hardware seems unable to
    transmit more than 800 kpps, so this increase appears to be
    limited almost solely by the hardware).  Gains have been shown in
    other workloads, ranging from better performance to elimination of
    over-saturation livelocks.
    http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/em/if_em.c#rev1.98


Perhaps you should spend a little less time thinking up ways to flame
people, and a little more time considering that just maybe FreeBSD is
developed by marginally competent people who are interested in and
capable of making progress.


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.