| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
increase version to 2.4.4
|
| | |
| |
| |
| | |
version prepere for the next release
|
| |\ \
| | |
| | | |
remove definition of `_mm256_set_m128i`
|
| | |/
| |
| |
| | |
The define of `_mm256_set_m128i` is not needed and avoid intel compiler throws a warning about it.
|
| |\ \
| |/
|/| |
fix duplicated nonce usage
|
| | |
| |
| |
| |
| |
| | |
- avoid that a nonce which not fits to the current job is used (check jobId after start nonce is consumed)
- move jobId check into the if condition to get a new bunch of nonces
- CPU: add jobId validation after the start nonce is consumed
|
| |\ \
| |/
|/| |
fix possible deadlock with Volta
|
| | |
| |
| |
| |
| |
| |
| | |
If CUDA 9.X is used and the miner is compiled for `sm_70` and used with Volta GPUs than the miner
deadlocks if `threads` is not a multiple of `32`.
- use `__activemask()` to get all active lanes
|
| | | |
|
| |\ \
| | |
| | | |
avoid out of order job processing
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The login result of a pool contains the first job for the miner.
In the case where the pool is sending very fast after the pool login result
a new job it is possible that the newer job is processed faster than the job within the login result.
The result will be that the miner is mining an older job instead the newest (last received).
- enumerate all received messages
- trace the message id of the last procssed job
- skip all jobs where the message id is older than the last procesed id
|
| | |
| |
| |
| |
| |
| | |
- reformat `read_write_lock.h`
- fix spelling issue
- move job id increase of the write to the buttom
|
| | |
| |
| |
| | |
user read write locks to be sure that no job is consumend during the job update
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
add log class from Will Zhang:
Package: cpputil
Source: https://github.com/willzhang4a58/cpputil
License: MIT License
|
| |/
|
|
|
|
|
|
|
| |
fix #1505
- fix possible deadlock of the executor thread
- fix racecondition during the job consumation
- remove switch_work in all classes `minethd`
- move `consume_work` into `globalStates`
|
| |\
| |
| | |
ignore duplicated equal job from pools
|
| | |
| |
| |
| |
| |
| |
| | |
Some pools or proxys are sending multiple times in row the same job to the miner.
This PR will extent the miner to trigger an socket error if job with the same `jobID` than the current active job is received.
Move motd evaluation before the possibil part where a job is ignored.
|
| |\ \
| | |
| | | |
fix possible race condition in jpsock
|
| | | |
| | |
| | |
| | | |
Trigger event with a new job after the current pool job is updated.
|
| | |/
|/| |
|
| |\ \
| |/
|/| |
set correct `iPoolId` for miner_work
|
| | |
| |
| |
| |
| | |
- initialize miner_work iPoolId in the default constructor with the invalid pool id
- move definition of `pool_data` into an own file
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
solve #1494
- add algorithm `cryptonight_v7_stellite` (internal named: `cryptonight_stellite`)
|
| |\
| |
| | |
fix that cli option `--noAMDCache`
|
| | |
| |
| |
| | |
- fix that to much OpenCL calls whre used if cache is disabled
|
| |\ \
| | |
| | | |
Small typo correction
|
| | |/ |
|
| | |
| |
| |
| | |
changes printed algorithm names to algorithms exposed to the used instead of internal used names
|
| |/
|
|
|
| |
- add algorithm `cryptonight_lite_v7_xor`
- update documentation
|
| |\
| |
| | |
Add turtlecoin as a config option
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| | |
BBSCoin support and get ready for cryptonight v7 upgrade
|
| | |
| |
| |
| |
| |
| | |
- fix dev pool algorithms
- add note to `pools.tpl`
- remove pool suggestion
|
| | | |
|
| | | |
|
| |/
|
|
| |
Official Announcement: https://intensecoin.com/2018/04/16/imminent-hard-fork-and-network-attack/
|
| |
|
|
|
|
|
|
|
|
|
|
| |
clang warns about the wrong usage:
```
```
xmrstak/net/jpsock.cpp:232:30: warning: parentheses were disambiguated as redundant parentheses around declaration of variable named 'job_mutex' [-Wvexing-parse]
std::unique_lock<std::mutex>(job_mutex);
^~~~~~~~~~~
xmrstak/net/jpsock.cpp:232:30: note: add a variable name to declare a 'std::unique_lock<std::mutex>' initialized with 'job_mutex'
std::unique_lock<std::mutex>(job_mutex);
```
|
| | |
|
| |
|
|
| |
remove fork version for sumokoin and monero7
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- allow the dev pool to fork on a different block version than the user descriped coin
All algorithm are centered around the user coin description.
It is allowed to have two two different coin algorithms in the user coin description.
It is only allowed to use algorithms for the dev pool coin description those are used in the user coin description.
There are two ways to define a non forking coin.
- set both user coin algorithm descriptions to the same algorithm and set version to zero
- set the first algorithm in the user coin description to something you like to use in the dev pool
and set the second algorithm to the correct representation of the coin. Set the version to 255.
This will allow that the dev pool can mine on a different coin algorithm than the not forking user coin.
Do not use an algorithm with different scratchpad size for the dev pool.
|
| |
|
|
|
| |
In the case where the dev pool mines on a higher version than a monero fork coin the miner is not resetting the algorithm.
This PR select the correct algorithm each time the block version hash changed.
|
| |\
| |
| | |
allow non AMD OpenCL driver and devices
|
| | |
| |
| |
| |
| |
| | |
- add CLI flag to explicitly use non AMD OpenCL and devices
- adjust OpenCL output (use OpenCL instead of AMD if --altOpenCL is sued)
- optimize NVIDIA OpenCL auto suggestion
|
| |\ \
| | |
| | | |
expose original algorithm
|
| | |/
| |
| |
| |
| | |
- expose cryptonight_lite_v7, cryptonight_heavy and cryptonight_v7
- remove cryptonight_lite
|
