Skip to content
Snippets Groups Projects
Commit b8cded77 authored by psychocrypt's avatar psychocrypt Committed by GitHub
Browse files

Merge pull request #260 from notunderground/dev

fix typos in config.txt
parents b64d5851 f2c8f0cc
No related branches found
No related tags found
No related merge requests found
...@@ -27,8 +27,8 @@ null, ...@@ -27,8 +27,8 @@ null,
/* /*
* LARGE PAGE SUPPORT * LARGE PAGE SUPPORT
* Large pages need a properly set up OS. It can be difficult if you are not used to systems administation, * Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
* but the performace results are worth the trouble - you will get around 20% boost. Slow memory mode is * but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
* meant as a backup, you won't get stellar results there. If you are running into trouble, especially * meant as a backup, you won't get stellar results there. If you are running into trouble, especially
* on Windows, please read the common issues in the README. * on Windows, please read the common issues in the README.
* *
...@@ -53,13 +53,13 @@ null, ...@@ -53,13 +53,13 @@ null,
* and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT * and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
* recommended for security reasons. * recommended for security reasons.
* *
* Memory locking means that the kernel can't swap out the page to disk - something that is unlikey to happen on a * Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
* command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between * command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
* locked and unlocked memory. If that is your setup see option "no_mlck". * locked and unlocked memory. If that is your setup see option "no_mlck".
*/ */
/* /*
* use_slow_memory defines our behaviour with regards to large pages. There are three possible options here: * use_slow_memory defines our behavior with regards to large pages. There are three possible options here:
* always - Don't even try to use large pages. Always use slow memory. * always - Don't even try to use large pages. Always use slow memory.
* warn - We will try to use large pages, but fall back to slow memory if that fails. * warn - We will try to use large pages, but fall back to slow memory if that fails.
* no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory. * no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
...@@ -70,7 +70,7 @@ null, ...@@ -70,7 +70,7 @@ null,
/* /*
* NiceHash mode * NiceHash mode
* nicehash_nonce - Limit the noce to 3 bytes as required by nicehash. This cuts all the safety margins, and * nicehash_nonce - Limit the nonce to 3 bytes as required by nicehash. This cuts all the safety margins, and
* if a block isn't found within 30 minutes then you might run into nonce collisions. Number * if a block isn't found within 30 minutes then you might run into nonce collisions. Number
* of threads in this mode is hard-limited to 32. * of threads in this mode is hard-limited to 32.
*/ */
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment