summaryrefslogtreecommitdiffstats
path: root/xmrstak/backend/amd/autoAdjust.hpp
Commit message (Collapse)AuthorAgeFilesLines
* XMR-Stak 2.3.0 RCxmr-stak-devs2018-03-251-10/+2
| | | | | | | Co-authored-by: psychocrypt <psychocryptHPC@gmail.com> Co-authored-by: fireice-uk <fireice-uk@users.noreply.github.com> Co-authored-by: Lee Clagett <code@leeclagett.com> Co-authored-by: curie-kief <curie-kief@users.noreply.github.com>
* fix broken memchunk featurepsychocrypt2018-02-211-1/+1
| | | | fix double definition of define `MEM_CHUNK`
* add OpenCL compatibility modepsychocrypt2018-02-191-1/+2
| | | | | - add new option `comp_mode` to the amd config - disable `if guards` within opencl kernel if `comp_mode : false`
* AMD: `mem_chunk`and new `strided_index`psychocrypt2018-02-171-1/+1
| | | | | - add new option for `strided_index` - add additional option if `strided_index == 2` to controll the memory chunk with
* improve AMD auto suggestion for AEONpsychocrypt2018-01-301-0/+3
| | | | increase the intensity limit for AEON
* Merge pull request #758 from dougvj/fix_zero_intensityfireice-uk2018-01-271-9/+21
|\ | | | | Add warning and fallback when auto intensity is 0
| * ignore gpu with intensity zeropsychocrypt2018-01-131-18/+17
| | | | | | | | | | - if the intensity is zero than do not suggest a config - remove the links to old issues
| * Add warning and fallback when auto intensity is 0Doug Johnson2017-12-311-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Occassionally the auto adjust doesn't find enough memory and the intensity is detected too low and aligned to 0 with the compute units. This patch fixes this situation by issuing a warning with a suggestion to set environment vars and then ignoring the alignment to 0 Per several issues: Principally: https://github.com/fireice-uk/xmr-stak/issues/81 Related: https://github.com/fireice-uk/xmr-stak/issues/490 https://github.com/fireice-uk/xmr-stak/issues/472
* | update VEGA names for auto suggestionpsychocrypt2018-01-091-1/+10
|/ | | | update VEGA names
* set `srided_index = true` as defaultpsychocrypt2017-12-031-1/+1
| | | | Change the default for strided index. Th euser feedback shows that strided_index = true will give a view hashes more per second.
* add AMD scratchpad indexing optionpsychocrypt2017-12-021-1/+1
| | | | | | Allow to change the indexing used to address the hash scratchpad memory. - add option `strided_index` for each gpu
* remove space indention with tabspsychocrypt2017-11-161-27/+27
| | | | - removed all space indention in `*.hpp` and `*.cpp` files
* tune VEGA auto suggestionpsychocrypt2017-10-271-3/+15
| | | | | | - allow to use up to 2024 threads on VEGA gpus fix #5
* increase safety memory for autosuggestionpsychocrypt2017-10-271-2/+2
| | | | | - increase safty memory from 64 to 128 MiB - NVIDIA: increase lmem reserve per thread to 1kiB
* rename `xmr` to `monero`psychocrypt2017-10-271-4/+4
| | | | | | - rename all `xmr` to `monero` - be insensitive while check for set currency - add function to compate two strings insensitive
* add eon support to amd backendpsychocrypt2017-10-271-1/+13
| | | | | - add compile parameter to support aeon and xmr - update auto suggestion to handle aeon
* remove the gpu_thread_num safetyfireice-uk2017-10-121-1/+0
|
* improve AMD auto suggestionpsychocrypt2017-10-101-2/+7
| | | | | - use always a multiple of the number of compute units - add more device information to the config file
* fix amd auto suggestionpsychocrypt2017-10-041-3/+5
| | | | | | Platform index zero was always used to search for the device detection. Fix: use correct detected AMD platform index
* nvidia: fix return value if no device is foundpsychocrypt2017-09-301-4/+2
|
* rename `Params` to `params`psychocrypt2017-09-301-2/+2
|
* fix compilepsychocrypt2017-09-301-1/+1
|
* cleanup includespsychocrypt2017-09-301-6/+5
|
* group filespsychocrypt2017-09-301-0/+114
- move source code to `src` - categorize files and move to group folder - change upper case class files to lower case - change C++ header to `*.hpp`
OpenPOWER on IntegriCloud