Getting (MemLock) "Cannot Allocate Memory" on LockedBuf::with_size()

Question

Getting (MemLock) "Cannot Allocate Memory" on LockedBuf::with_size()

Closed this issue 4 years ago · 5 comments

theli-ua commented 4 years ago

Any idea on how to debug this? I'm requesting a fairly small size ~200000

Answer 1 · 2020-07-11T10:02:02.000Z

Could be some OS limits. Take a look here: https://stackoverflow.com/questions/27634109/why-mmap-cannot-allocate-memory

Answer 2 · 2020-07-11T16:47:49.000Z

Its from lock, not mmap.

Either way I figured, Its a user limit on locked memory in my case. ( ulimit -l )

Answer 3 · 2020-07-11T16:50:56.000Z

Would it possible to make LockedBuf a trait so that a user could provide a different implementation?

Answer 4 · 2020-07-12T10:42:04.000Z

What is the goal? Linux AIO requires the memory to be locked so that it never gets swapped out. Any ideas why implementation may be different?

Answer 5 · 2020-07-18T06:25:09.000Z

@glebpom for example someone could maintain its own pool of preallocated mapped regions that they would want to reuse instead of doing an mmap every time