Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Sep 2007 21:46:02 +1000
From:      Norberto Meijome <freebsd@meijome.net>
To:        Richard A Steenbergen <ras@e-gerbil.net>
Cc:        freebsd-net@freebsd.org
Subject:   Re: Quagga as border router
Message-ID:  <20070921214602.38487d27@meijome.net>
In-Reply-To: <20070921035449.GC1906@gerbil.cluepon.net>
References:  <46F1AC0B.9040109@ibctech.ca> <46F1BDE1.8090102@gmail.com> <46F1E900.7070604@elischer.org> <46F1F376.3020609@ibctech.ca> <20070920072409.GT79417@elvis.mu.org> <20070920114839.M37866@swaggi.com> <20070921035449.GC1906@gerbil.cluepon.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Sep 2007 23:54:49 -0400
Richard A Steenbergen <ras@e-gerbil.net> wrote:

> Honestly, FreeBSD routing code is pretty poor as far as a modern router 
> goes. If you throw enough CPU at it you can brute force your way through 
> plenty of things, but in the context of modern commercial routers it 
> doesn't even play in the same league (even for a software-only router).

Interesting.... what is the golden aim of software based router we should be
trying to reach? 

IMHO, comparing routing code in software vs. hardware routing, or vs
a RTOS seems a bit useless (unless the comparison is something like 'we could
do things much faster this way, but that would force us to go down the path of
hard RT OS..) Which is different to saying 'well, this and that part of x and Y
are inefficient / too expensive for the latest cpu models."

I'm not bagging you , but there's always the balance to be had - something very
flexible (as *BSD / Linux ) vs something very rigid (programmatically) but very
fast / scalable... i'm interested in seeing how / whether we efficiency can be
increased without losing the flexibility (of course, @ the cost of
time,etc...something needs to give :D )

cheers,
B
_________________________
{Beto|Norberto|Numard} Meijome

"He loves nature in spite of what it did to him."
  Forrest Tucker

I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.



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