Skip to content

Commit

Permalink
fix typos in config.txt
Browse files Browse the repository at this point in the history
  • Loading branch information
notunderground committed Jul 31, 2017
1 parent b64d585 commit f2c8f0c
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions config.txt
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,8 @@ null,

/*
* LARGE PAGE SUPPORT
* Large pages need a properly set up OS. It can be difficult if you are not used to systems administation,
* but the performace results are worth the trouble - you will get around 20% boost. Slow memory mode is
* Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
* 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
* on Windows, please read the common issues in the README.
*
Expand All @@ -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
* 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
* 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:

This comment has been minimized.

Copy link
@fogoat

fogoat Nov 1, 2017

behaviour is chiefly British spelling. It is not a typo. .

This comment has been minimized.

Copy link
@notunderground

notunderground Nov 3, 2017

Author

thanks

* 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.
* 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.
Expand All @@ -70,7 +70,7 @@ null,

/*
* 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
* of threads in this mode is hard-limited to 32.
*/
Expand Down

0 comments on commit f2c8f0c

Please sign in to comment.