Hi Alexander,
In short, the system executes a CPU-bounded workload spends a lot of
time in the idle thread, which is a contradiction. On CPU-bounded work
loads, the idle thread should never be selected by the scheduler. For
your tests, you may check how much time was spent in the idle thread via
the Fiasco.OC kernel debugger (use 'lp', select the idle thread). As
long as we see the idle thread being scheduled, we should not look too
much into micro-optimizing any code paths.
In short, we think that there is not much to gain (in terms of
performance) from distributing I/O bounded work to multiple CPU threads.
Fortunately, I can report that there is work under way to equip Genode
with a tracing infrastructure, which will allow us to gather traces
about RPCs (including the actual RPC function names), contended locks,
and signals. The new facility is currently developed by Josef Söntgen
(cnuke at GitHub). We plan to include it in Genode 13.08.
Cheers
Norman
--
Dr.-Ing. Norman Feske
Genode Labs
http://www.genode-labs.com · http://genode.org
Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Genode-main mailing list
Genode-main@...12...ceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main