thats a gpu distro (nvidia), right? no oob cpuminer support afaik

i have also found the following stated from microsoft about large pages:

Large-page memory regions may be difficult to obtain after the system has been running for a long time because the physical space for each large page must be contiguous, but the memory may have become fragmented. Allocating large pages under these conditions can significantly affect system performance. Therefore, applications should avoid making repeated large-page allocations and instead allocate all large pages one time, at startup.

The memory is always read/write and nonpageable (always resident in physical memory).

The memory is part of the process private bytes but not part of the working set, because the working set by definition contains only pageable memory.

Large-page allocations are not subject to job limits.


that might be also the case for linux where its often advised to set the hugepage size on boot (in grub)

you will probably need to write a wrapper function for the allocation part to handle linux/windows differences

afaik the systemspecific code (that being hugetlbfs and largepages for ms) has to be written anyways if you want it to be included in any distro, the distro just takes away the os setup (which is easy), or have i missed something?

i meant distros with cpumining option already available

i dont know if this is the desired behaviour, but in the HOWTO the following is stated:

If that's the case maybe I don't need to change anything in cpuminer.

Edit: It looks like tranparent large pages is the way to go, and should have been from the start.
It wasn't so complicated when disk drives increased their block size.

From my understanding of MMU and TLB from another architecture...
From the application perspective accessing huge pages is just derefeferencing a pointer like any other data
access. The magic happens when the CPU executes the load instruction and translates that pointer to a physical
memory address. The only difference is the accesses are faster because the translation is cached and
the same cached trasnslation can be used for the entire larger page before a new mapping is required for the next page.
At a higher level fewer TLBs can access more memory.

Reserving a section of memory for large pages and using the file system to access it may provide benefits beyond
large pages, though I don't see how. I would think going through the file system would add extra overhead.

Some of my old theory is coming back so while I'm on a roll...

Fragmentation should be less of an issue with pure HP because each page is guaranteeed to be contiguous,
and being all the same size can always find a fit. However, memory bloat will occur because every app's
VM size will be rounded up to the next page.

In a hybrid environment the huge page is just a container (pool)  for many small pages. As long as small pages
are preallocated from the pool in groups they will not cause problems for the huge pages. Things only go bad
when a scattering of small pages results in difficulty finding a contiguous block big enough for a huge page.
As long as containers are used they all fit together nicely just like on a ship.

Edit: Still rolling

Some of the large pages will be nearly empty if they belong to apps with low memory requirenents. Being able
to allocate small pages for these apps means they can share a big page container reducing gaps and increasing
memory efficiency.

Hmq1725 Algo isn't working. Says stack smashing detected.

all algos work just fine except for that one. Was trying to mine doubloons on suprnova and it just crashes immediately after the difficulty shows up. Tried it on multiple computers. I'm on linux

I have the newest and the one you asked if I had. Both do the same thing. It broke as soon as I tried to mine the coin. I'm on Ubuntu 16.04. I have a i5-2450. Miner works perfect in Windows but I'd rather run it in Linux. I used ./build.sh and the ./autogen.sh way. Both compiled fine but crash the same way.

i really do apologize for being a pain in the ass. I compiled on Ubuntu 16.04. i hope this is the output your asking for. If not how do i find the other
name@name-VPCEH32FX:~/cpuminer-opt$ ./cpuminer -a hmq1725 -o stratum+tcp://boat.suprnova.cc:4156 -u twiztid1.2 -p x -t 2

      **********  cpuminer-opt 3.5.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU:        Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz
CPU features: SSE2 AES AVX
SW built on Feb 19 2017 with GCC 5.4.0
SW features: SSE2 AES AVX
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2 AES AVX

[2017-02-19 13:30:09] Starting Stratum on stratum+tcp://boat.suprnova.cc:4156
[2017-02-19 13:30:09] Binding thread 0 to cpu 0 (mask 1)
[2017-02-19 13:30:09] 2 miner threads started, using 'hmq1725' algorithm.
[2017-02-19 13:30:09] Binding thread 1 to cpu 1 (mask 2)
[2017-02-19 13:30:09] Stratum session id: deadbeefcafebabe382b000000000000
[2017-02-19 13:30:12] stratum extranonce subscribe timed out
[2017-02-19 13:30:12] DEBUG: job_id='8e47' extranonce2=00000000 ntime=58a9f235
[2017-02-19 13:30:12] Stratum difficulty set to 1 (0.00002)
[2017-02-19 13:30:12] hmq1725 block 29228, diff 3.345
[2017-02-19 13:30:13] DEBUG: hash <= target
Hash:   00004bd64e027695caea3732e8c8c775d6c12260d3829714b213d30aa27f960d
Target: 0000ffff00000000000000000000000000000000000000000000000000000000
*** stack smashing detected ***: ./cpuminer terminated
Aborted (core dumped)
name@name-VPCEH32FX:~/cpuminer-opt$