Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Setting /etc/security/limits.conf per FAQ leads to LVM problem (and what is utility of mmap?) #514
I updated limits.conf per the FAQ, with the lines:
But then when I logged out and tried to log in again, I got an lvmedad error and no X session. I also tried setting use_lvmedad to 0, but then I simply got a non-functional X session explaining that it couldn't detect card or peripherals. I couldn't even respond to dialogs. Commenting these lines got rid of the problem. And also, if I just use my username instead of * in limits.conf, this gets rid of the problem.
Based on this stackoverflow question, I'm guessing this is just general bugginess in LVM, but it seems worth reporting in case other users run into this issue. It's rather debilitating! (note, this is NOT the same problem, and the fix on stack overflow - which I describe trying above - doesn't work.)
In any case, restricting to my username seems to safely up my memory limits and the mmap errors go away. However, it's not clear it helps performance much! On my CPU even when I restrict to the first four cores, and all report successfully pinning memory, I only get about 77 H/s per core. Memory does not get pinned for (logical) cores 4-7. I do understand that using all cores cripples performance (using 15 of 16 I only had ~15 H/s per core). Similarly, when I only use (logical) cores 0-4 and 8-11, memory gets pinned for all of them, but performance is still ~15 H/s.
I'm curious if I can get better performance out of this threadripper. In particular, if I should be messing with NUMA or not.
In any case, thanks for the tool! It's sending a little hashing your way ;)
sudo sysctl -w vm.nr_hugepages=128
Issue with the execution
AMD OpenCl issue