Hi Norman<div><br></div><div>Thanks for the insights. I still don't understand why init's(?) quota exceeds. I get the warning no matter of the presence of the "overly large quantum". Is this behavior intended?</div><div><br></div><div>- How big is the initial quota of init?</div><div><br></div><div>- Can I change that quota - or only the preserved slack memory?</div><div><br></div><div>- If not - is there another way to prevent the "Quota exceeded!" warning?</div><div><br></div><div>- Does the size of the metadata allocation for a child depends on whether I'm using a 32 or 64 bit system?</div><div><br></div><div>- Is a scenario with 19 or more components within one init considered 'large'?</div><div><br></div><div>Thanks,</div><div>Roman</div><div><br></div><div><br>On Mit, Okt 5, 2016 at 9:05 , Norman Feske &lt;norman.feske@...1...&gt; wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">Hi Roman,

On 04.10.2016 20:04, Roman Iten wrote:
<blockquote> Hi, I wrote a simple run script 'manytimer', based on 'timer':
 <a href="https://github.com/rite/genode/tree/manytimer">https://github.com/rite/genode/tree/manytimer</a>. When the number of
 components exceeds 19, I get a "Quota exceeded!" warning. It seems that
 it doesn't matter if I use timer or other components. It also doesn't
 matter how much RAM quota I configure per timer. - Is this behaviour
 intended? - Whose quota exceeds (init, core, ...)? - Can I resolve the
 warning by increasing its quota? - In a scenario with 19 or more
 components (within one init), is it still possible to "assign all
 remaining resources to the last child by simply specifying an overly
 large quantum" as described in "Genode 16.05 Foundations" (see Chapter
 6.2.2 "Resource quota saturation"). Or would there be no more slack
 memory available for init and core respectively?
</blockquote>
I encountered the same problem in the Turmvilla scenario. In the
presence of the "overly large quantum", init transfers all remaining
quota from itself to the corresponding child and preserves just a tiny
bit of quota for itself. This preserved quota is needed to accommodate
the few metadata allocations that cannot be easily allocated from a
specific child (i.e., child-thread meta data). If the number of children
becomes too large, this preservation does not suffice. But you can
increase the value as done by the following commit:


<a href="https://github.com/nfeske/genode/commit/619ce3ff2c81df8e24b10a675ccc78b83ee30e7f">https://github.com/nfeske/genode/commit/619ce3ff2c81df8e24b10a675ccc78b83ee30e7f</a>

Cheers
Norman

<div>-- 
</div>Dr.-Ing. Norman Feske
Genode Labs

<a href="http://www.genode-labs.com">http://www.genode-labs.com</a> · <a href="http://genode.org">http://genode.org</a>

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! <a href="http://sdm.link/slashdot">http://sdm.link/slashdot</a>
_______________________________________________
genode-main mailing list
<a href="mailto:genode-main@lists.sourceforge.net">genode-main@...12...ceforge.net</a>
<a href="https://lists.sourceforge.net/lists/listinfo/genode-main">https://lists.sourceforge.net/lists/listinfo/genode-main</a>
</div></blockquote></div>