On 5/28/2015 11:35 AM, Paul Jakma wrote:
On Thu, 28 May 2015, Lennart Sorensen wrote:
As someone working on small embedded level boxes without lots of cpu
cores, the separate process per VRF is not desirable at all. One
process with one config interface running in multiple namespaces is
ideal for us (and in fact what we are currently working on doing).
If someone wants to support multiple processes as well, that's fine,
as long as it works with a single process too for those that are not
interested in the multi core scalability and associated overhead of
multiple processes.
Exactly how constrained are you that the kernel process descriptors,
additional page tables and context switches are an issue?
But you are doing this for every daemon for every VRF, things add up
really quick. In a small experiment that I'm running now Quagga (zebra,
ospfd, pimd) uses 9MB of RAM. if I start adding VRFs I'm going to hit
a wall really quick.
Even parts of the embedded space are going multi-core now.
Other parts are single-core, both approaches single/multi daemon
have their best use cases.
Regards,
Jafar
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
