-
Notifications
You must be signed in to change notification settings - Fork 20.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gpu miner #1263
Gpu miner #1263
Conversation
ab8c956
to
90a209b
Compare
|
// #endif | ||
// #cgo CFLAGS: -I/opt/opencl-headers/include | ||
// #cgo darwin LDFLAGS: -framework OpenCL | ||
// #cgo LDFLAGS: -lOpenCL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Gustav-Simonsson You need to change this in the base repo to something like #cgo linux LDFLAGS: -LOpenCL
. This does not work on OS X. The already present -framework
is the same as -l -L -i -I
(gpubench doesn't crash anymore! it was an opencl configuration issue for me) |
@Gustav-Simonsson it only works with Although I run it with
Note also the option Then after |
90a209b
to
4a2757d
Compare
Complied after adding #include "CL/cl.h" to files. works but ignores secondary cards /miner/go-ethereum/build/bin/geth --minegpu --minerthreads 2 --autodag --datadir.... |
4a2757d
to
0cf0389
Compare
Getting the following error
|
0cf0389
to
ca9624b
Compare
@obscuren try re-fetching branch, pushed a fix to gpubench, should work as expected now. |
ca9624b
to
88043f4
Compare
…#1263) ### Description This changes the `light.serve` default back to zero so that serving light clients becomes opt-in rather than opt-out. The reason is that there are many use-cases for running a node that don't involve light clients, and only one use-case that is about serving light clients, so it makes more sense to have it opt-in to avoid people running the light server without realizing it. ### Other changes * Change `light.maxpeers` default value from 99 back to 100 (the change to 99 was to work around an issue that no longer exists, see below under "Related issues") * Fix a bug in the logic for the `lightPeers` variable in `SetP2PConfig()` (it was not respecting the default value of LightPeers, leading to incorrect values in the `Maximum peer count` log line and to `MaxPeers` not being increased when it should have been. ### Tested * Automated tests pass * Without specifying any flags, LES is off, max peers is 175 * Specifying `--light.serve 100`, LES is on, total max peers is 275, max eth peers is 175, max light peers is 100 * Specifying `--light.serve 100 --light.maxpeers 200`, LES is on, total max peers is 375, max eth peers is 175, max light peers is 200 * Specifying `--light.serve 100 --maxpeers 150`, LES is on, total max peers is 250, max eth peers is 150, max light peers is 100 * Specifying `--light.serve 100 --light.maxpeers 1000 --maxpeers 100`, LES is on, total max peers is 1100, max eth peers is 100, max light peers is 1000 (these are the flag values recommended in the docs for serving light clients, and are based on the fact that if (and only if) you specify both `light.maxpeers` and `maxpeers` then `maxpeers` is assumed to include `light.maxpeers`) ### Related issues - Closes ethereum#1262 - Additional context: ethereum#395, ethereum#416, ethereum#864 ### Backwards compatibility Breaking change to the defaults, most notably `--light.serve`, but with limited impact, because in the docs for running a full node we specify `--light.serve`, `--light.maxpeers` and `--maxpeers`, so it's not relying on the defaults anyway. And for users who are not intending to serve light clients, the new defaults make more sense.
EDIT: branch moved to https://github.com/ethereum/go-ethereum/tree/gpu_miner
Please run:
If it works you can then try with:
and then add the GPU mining flag.
NOTE:
Ubuntu OpenCL instructions: http://wiki.tiker.net/OpenCLHowTo