From 04cbee4c767319cd5dab1d456eb25c368a1cf27e Mon Sep 17 00:00:00 2001
From: Norman Feske <norman.feske@genode-labs.com>
Date: Mon, 14 Oct 2013 14:41:39 +0200
Subject: [PATCH] terminal_mux.run: Let CLI monitor preserve RAM

This change allows for the testing of cli_monitor's automatic resource
balancing by executing the following command:

  start ram_eater --ram-limit 1G --count 5

The command starts 5 instances of a RAM-eating process, which is,
however, able to yield resources when instructed. The RAM quota for the
processes gets automatically extended because of the overly large limit
of 1 GiB, which is far more than CLI monitor's RAM resources (100 MiB).
When the RAM usage hits the preservation limit, CLI monitor broadcasts
yield requests to each ram_eater instance, which allow the scenario to
remain alive.
---
 gems/run/terminal_mux.run | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/gems/run/terminal_mux.run b/gems/run/terminal_mux.run
index ba8319e08..8e61b8f7d 100644
--- a/gems/run/terminal_mux.run
+++ b/gems/run/terminal_mux.run
@@ -89,10 +89,11 @@ append config {
 			</route>
 		</start>
 		<start name="cli_monitor">
-			<resource name="RAM" quantum="1G"/>
+			<resource name="RAM" quantum="100M"/>
 			<config>
+				<preservation name="RAM" quantum="16M" />
 				<subsystem name="noux" help="VIM executed in the noux runtime">
-					<resource name="RAM" quantum="16M"/>
+					<resource name="RAM" quantum="16M" />
 					<config>
 						<fstab> <tar name="vim.tar" /> </fstab>
 						<start name="/bin/vim">
@@ -128,7 +129,7 @@ append config {
 				<subsystem name="ram_eater" help="resource-yield test program">
 					<resource name="RAM" quantum="25M" />
 					<binary name="test-resource_yield" />
-					<config child="yes" expand="yes" />
+					<config child="yes" expand="yes" period_ms="100" />
 				</subsystem>
 			</config>
 			<route>