Hi Roman,
> I agree. Making the preservation configurable makes the memory
> reservations more transparent, i.e. everything that requires memory is
> visible in init's configuration - well, at least if init is used in a
> static way. Or are there still other memory 'pools' one might not be
> a
Hi
Thank you very much for this very good explanation.
On 07.10.2016 10:47, Norman Feske wrote:
> In the shorter term, it would be sensible to make the preservation
> configurable via init's configuration instead of hard-coding the value.
> I plan to rework init soon and will keep this suggestion
Hi Ben,
thanks for chiming in!
On 05.10.2016 22:22, Nobody III wrote:
> Maybe init should have an XML option
> to set its reserved RAM quota, or it could instead automatically
> calculate the required quota based on the number of components it
> starts.
The automatic calculation would work if in
Hi Roman,
> How can I distinguish if the condition is handled properly or not? Are
> there any preceding or following log messages in either case?
I remember the following situations where the messages were somehow
useful to diagnose a problem:
- If the scenario got stuck with the this being the
I've had problems with init failing when a component was configured to use
all remaining available RAM. I've had to alter some of the standard run
scripts to make them work. I don't remember which ones right now, but I
think arora was one of them. Maybe init should have an XML option to set
its res
Hi Norman
- How big is the initial quota of init?
init receives the quota for all the available physical memory from
core.
The amount depends on the physical memory of the machine. It is
printed
by core when init is started.
Thats what I thought. But I couldn't imagine how init's quota c
Hi Roman,
> - How big is the initial quota of init?
init receives the quota for all the available physical memory from core.
The amount depends on the physical memory of the machine. It is printed
by core when init is started. Look for a message like this:
24 MiB RAM assigned to init
> - Can
Hi Norman
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?
- How big is the initial quota of init?
- Can I change that quota - or only the preserved slack memor
Hi Roman,
On 04.10.2016 20:04, Roman Iten wrote:
> Hi, I wrote a simple run script 'manytimer', based on 'timer':
> https://github.com/rite/genode/tree/manytimerWhen 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
