Bug#474648: please re-enable CONFIG_SECCOMP, it's harmless (and needed)
On Mon, Apr 07, 2008 at 07:51:41AM +0000, maximilian attems wrote:
> that is a commercial entity, no need to push that.
> unless something substantial comes up that bug can be close right away.
It seems that you're not really forced to use the commercial side. CPUShare
may be use freely if you want to give CPU time for some free projects which
Is there some real-word benchmark about SECCOMP impact on performances?