Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

init: ram quota as start-node attribute #5448

Open
nfeske opened this issue Feb 7, 2025 · 1 comment
Open

init: ram quota as start-node attribute #5448

nfeske opened this issue Feb 7, 2025 · 1 comment
Labels
feature fixed

Comments

@nfeske
Copy link
Member

nfeske commented Feb 7, 2025

In init's configuraton, the assignment of RAM to a component is expressed as follows:

<start name="report_rom">
  ...
  <resource name="RAM" quantum="2M"/>
  ...
</start>

Let's support a new ram attribute as a shortcut.

<start name="report_rom" ram="2M">
  ...
</start>

This approach is already employed in Sculpt's deploy config. So init should follow suit.
@nfeske nfeske added the feature label Feb 7, 2025
nfeske added a commit that referenced this issue Feb 11, 2025
@nfeske
init: ram quota as start-node attribute
1bbda2b 
This patch allows for the assignment of RAM to a start node via a new
'ram' attribute as an alternative to traditional '<resource name="RAM">'
nodes. This makes configurations more concise.

It also adds support for defining a configuration-global default RAM
quota, following the existing pattern of the default caps definition,
e.g. the following <default> node alleviates the need to repeatedly
state reasonable 'ram' and 'caps' values in each single start node.

  <default caps="100" ram="1M"/>

Fixes #5448
nfeske added a commit that referenced this issue Feb 11, 2025
@nfeske
run: use ram attribute in start nodes
17cba51 
Issue #5448
nfeske added a commit to genodelabs/genode-allwinner that referenced this issue Feb 11, 2025
@nfeske
run: use ram attribute in start nodes
6facc82 
Issue genodelabs/genode#5448
nfeske added a commit to genodelabs/genode-imx that referenced this issue Feb 11, 2025
@nfeske
run: use ram attribute in start nodes
8adbe0e 
Issue genodelabs/genode#5448
nfeske added a commit to genodelabs/genode-zynq that referenced this issue Feb 11, 2025
@nfeske
run: use ram attribute in start nodes
31f0fa1 
Issue genodelabs/genode#5448
nfeske added a commit to genodelabs/genode-rpi that referenced this issue Feb 11, 2025
@nfeske
run: use ram attribute in start nodes
45ea28d 
Issue genodelabs/genode#5448
nfeske added a commit to genodelabs/genode-riscv that referenced this issue Feb 11, 2025
@nfeske
run: use ram attribute in start nodes
f9b283d 
Issue genodelabs/genode#5448
@nfeske nfeske added the fixed label Feb 11, 2025
@nfeske
Copy link
Member Author

nfeske commented Feb 11, 2025

Implemented by 1bbda2b.
Configurations adapted by 17cba51, genodelabs/genode-allwinner@6facc82, genodelabs/genode-imx@8adbe0e, genodelabs/genode-zynq@31f0fa1, genodelabs/genode-rpi@45ea28d, and genodelabs/genode-riscv@f9b283d.

chelmuth added a commit that referenced this issue Feb 12, 2025
@chelmuth
fixup "run: use ram attribute in start nodes" (typos)
5a28fee 
Issue #5448
nfeske added a commit that referenced this issue Feb 12, 2025
@nfeske
fixup "run: use ram attribute in start nodes" (test-timer)
a602f31 
Issue #5448
nfeske added a commit that referenced this issue Feb 12, 2025
@nfeske
fixup "run: use ram attribute in start nodes" (test/libc_fifo_pipe)
582d661 
Issue #5448
nfeske added a commit that referenced this issue Feb 12, 2025
@nfeske
fixup "run: use ram attribute in start nodes" (file_vault_client.run)
11c07c8 
Issue #5448
nfeske added a commit that referenced this issue Feb 12, 2025
@nfeske
fixup "run: use ram attribute in start nodes" (vfs_tresor.run, lx_hyb…
75aaab5 
…rid_pthread_ipc.run)

Issue #5448
chelmuth added a commit that referenced this issue Feb 13, 2025
@chelmuth
fixup "run: use ram attribute in start nodes" (typo in test-tcp_bulk_…
c24cc8b 
…lxip/runtime)

Issue #5448
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nfeske