ROCm / ROCm/FastFlowLM

Memlock not set to infinity

Open
#437 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.9k
Forks
152
Avg merge
4h 14m
Merged PRs (30d)
11

Description

Went through the deployment guide and have set the limits.conf to unlimited as it wasn't set to that.
Rebooted, but it still but the validate command still shows that the Memlock limit is not "infinity" like the output shown in the deployment guide.
Am i missing anything?

user@pop-os:/etc/security$ sudo flm validate
[Linux]  Kernel: 6.18.7-76061807-generic
[Linux]  NPU: /dev/accel/accel0 with 8 columns
[Linux]  NPU FW Version: 1.1.2.64
[Linux]  amdxdna version: 0.6
[Linux]  Memlock Limit: 2954 MB
user@pop-os:/etc/security$
user@pop-os:/etc/security$ ulimit -l
3025724
user@pop-os:/etc/security$

===========
After Reboot

user@pop-os:~$ sudo flm validate
[sudo] password for user:
[Linux]  Kernel: 6.18.7-76061807-generic
[Linux]  NPU: /dev/accel/accel0 with 8 columns
[Linux]  NPU FW Version: 1.1.2.64
[Linux]  amdxdna version: 0.6
[Linux]  Memlock Limit: 2954 MB <<<<<===============
user@pop-os:~$
user@pop-os:~$ ulimit -l
unlimited
user@pop-os:~$ 
user@pop-os:/etc/security$ cat limits.conf | grep memlock
#        - memlock - max locked-in-memory address space (KB)
*    soft    memlock    unlimited
*    hard    memlock    unlimited
user@pop-os:/etc/security$
Pop_OS! 24.04
user@pop-os:~$ uname -ra
Linux pop-os 6.18.7-76061807-generic #202601231045~1769703228~24.04~cb87b5b SMP PREEMPT_DYNAMIC Thu J x86_64 x86_64 x86_64 GNU/Linux
user@pop-os:~$

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the deployment guide, /etc/security/limits.conf, and the flm validate entry point. Compare the memlock limit reported by flm validate with the shell's ulimit -l after reboot and when running through sudo. Done should mean the documented configuration produces the expected infinity result, or the guide explains the observed 2954 MB limit.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.