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?
Even parts of the embedded space are going multi-core now.
It makes configuration management from another process much more work.
That's why we aren't doing that.
The destination assumes we fix that.
It's definitely an issue now, agreed. However, does that mean we should
allow our limitations to corner us?
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
"An ounce of prevention is worth a ton of code."
-- an anonymous programmer
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
