Skip to content

[FIX] - Add memory quotas to Docker runs#36

Open
Surya-Gunukula wants to merge 1 commit intoNVlabs:mainfrom
Surya-Gunukula:docker_quota
Open

[FIX] - Add memory quotas to Docker runs#36
Surya-Gunukula wants to merge 1 commit intoNVlabs:mainfrom
Surya-Gunukula:docker_quota

Conversation

@Surya-Gunukula
Copy link

Implement configurable memory limits for Docker containers to prevent runaway memory usage from incorrectly generated Verilog code.

Changes:

  • Add DOCKER_HARNESS_MEMORY_LIMIT and DOCKER_AGENT_MEMORY_LIMIT config options
  • Apply memory limits via --memory and --memory-swap flags in shell scripts
  • Memory limits applied to harness/evaluation containers (where iverilog runs)
  • Memory limits applied to agent containers (both code paths)
  • Backwards compatible: defaults to None (no limits if not configured)
  • Updated documentation in README_DEVELOPER.md and README_FULL.md

Closes #18

Implement configurable memory limits for Docker containers to prevent
runaway memory usage from incorrectly generated Verilog code.

Changes:
- Add DOCKER_HARNESS_MEMORY_LIMIT and DOCKER_AGENT_MEMORY_LIMIT config options
- Apply memory limits via --memory and --memory-swap flags in shell scripts
- Memory limits applied to harness/evaluation containers (where iverilog runs)
- Memory limits applied to agent containers (both code paths)
- Backwards compatible: defaults to None (no limits if not configured)
- Updated documentation in README_DEVELOPER.md and README_FULL.md

This addresses issue NVlabs#18 where incorrectly generated Verilog can cause
iverilog to consume excessive memory, leading to host system instability.

Signed-off-by: Surya Gunukula <suryagunukula@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add memory quotas to Docker runs

1 participant