Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
OBITools3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • OBITools
  • OBITools3
  • Issues
  • #20

Closed
Open
Opened Oct 02, 2015 by Celine Mercier@mercierOwner

Enlarging a mmapped region

When enlarging a mmapped region by giving the current pointer as first argument and mmapping on the next byte, if the MAP_FIXED flag was not set, I observed that the 'wish' to keep the same pointer is never fulfilled on my system, meaning that the system can never enlarge the mmapped region without overwriting other things, so the function that enlarges columns always ends up munmapping and mmapping again. If MAP_FIXED is set, the pointer is always kept and everything that was in the new enlarged region is overwritten no matter what, which sounds like a terrible idea (see this discussion http://stackoverflow.com/questions/3521303/is-there-really-no-mremap-in-darwin)

Should we keep trying to directly enlarge anyway (but it could be costly for a result that seems constantly negative)?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: obitools/obitools3#20