[EMAIL PROTECTED] writes: > It's not just the memory consumption you have to watch out for. Since each > vblade process opens a raw socket then that means for every packet > received there's a copy to memory and a context switch done to wake up > each and every one of those vblade processes.
This is no longer the case: I fixed this using BPF/linux socket filters in a patch that was distributed with vblade-16 and went into the main vblade codebase in vblade-18. A vblade instance will now only wake up for a AoE packet which is destined for the matching slot and shelf number. I'm exported several hundred AoE devices per host over gigabit ethernet, and see marginally better performance from a collection of vblade processes than a qaoed instance, despite the greater code complexity of the latter. Cheers, Chris. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Aoetools-discuss mailing list Aoetools-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
