Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
R
ramfs
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • redox-os
  • ramfs
  • Issues
  • #5

Closed
Open
Opened Apr 01, 2021 by Joshua Abraham@jabedudeDeveloper

ramfs maximum disk size

Just a drive-by thought, but wanted to discuss with @4lDO2. Should ramfs support a configuration option for maximum memory usage? Theoretically there is currently no upper bound for capacity. I think we should consider setting a limit for any ram filesystem and return ENOSPC once the limit is encountered. Thoughts?

Let's set a limit on maximum memory usage by the ramfs device to prevent memory pressure on the system. When the device reaches the upper bound, return ENOSPC. While a first pass may implement this globally, eventually we want to track usage per user to prevent any single user from using all memory backed storage

Edited Apr 01, 2021 by Joshua Abraham
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: redox-os/ramfs#5