 Con Kolivas
|
ad787e1c2a
Move the flushing of old work into restart threads so it's done before any worker threads grab more work.
|
14 years ago |
|
Con Kolivas
|
5007805d1f
Update CPU reentrant scan code to work properly for extended periods up to scantime and adjust rate properly.
|
14 years ago |
|
Con Kolivas
|
e4f9ea68a9
CPU mining is spending too much time in the work thread and not receiving restart messages.
|
14 years ago |
|
Con Kolivas
|
8999bea110
People expect miners to run indefinitely instead of giving up by default so change to never giving up if json call fails.
|
14 years ago |
|
Con Kolivas
|
9f726400d4
Logic error in the queueing of work ended up generating more stale blocks.
|
14 years ago |
|
Con Kolivas
|
594b38b8cb
Fix redefinition of gnu source.
|
14 years ago |
 Ycros
|
9fe2106467
Fixed up using config.h instead of cpuminer-config.h.
|
14 years ago |
|
Con Kolivas
|
edd0591e19
Make the number of queued work items configurable and default to 2.
|
14 years ago |
|
Con Kolivas
|
131f60a5ee
Move queueing of one request to separate function in preparation for variable length queues.
|
14 years ago |
|
Con Kolivas
|
ffdffe77d3
Make sure the work gets attributed to the correct gpu.
|
14 years ago |
|
Con Kolivas
|
86e40ed9c8
Stale block control makes it possible to make 2 threads per gpu the default again.
|
14 years ago |
|
Con Kolivas
|
48caf248a7
Check for stale block after failed submission as well.
|
14 years ago |
|
Con Kolivas
|
09104ce3e8
Flag the work back to just thread 0 used by all the threads to avoid lots of queued older work for each thread.
|
14 years ago |
|
Con Kolivas
|
bed692152f
Get rid of the requirement for a static struct that needs locking to cache work.
|
14 years ago |
|
Con Kolivas
|
e2fb3e84cb
Queueing all kernel parameters dramatically reduces stale block rates.
|
14 years ago |
|
ckolivas
|
7ae9afc40f
Profile points and warning clean ups.
|
14 years ago |
|
ckolivas
|
b54a342529
Change default number of threads back to 1. The 2nd just increases the time taken to complete a work item thus increasing stale blocks, despite increasing the rate slightly.
|
14 years ago |
|
Con Kolivas
|
88d9d631e3
Use two separate curl instances for submit and get and use separate threads for each to prevent one blocking the other.
|
14 years ago |
|
Con Kolivas
|
72baac0889
Clearly delineate the cpus from the gpus for their local data.
|
14 years ago |
|
Con Kolivas
|
142576a961
We already have gpu/cpu from id, so use that. Likely the current convoluted code is wrong and leading to segfaults!
|
14 years ago |
|
Con Kolivas
|
18f8b0f9a5
Submit work async is still unreliable and only used for cpu mining, so back it out for now.
|
14 years ago |
|
Con Kolivas
|
d5d4d1da16
Don't want to free the work data out of the transient structs.
|
14 years ago |
|
Con Kolivas
|
d100281df3
Make sure correct thread id is in work struct and correct cpu is set for per-cpu data.
|
14 years ago |
|
Con Kolivas
|
998d8d45f4
Postcalc hash is already its own thread so work can be submitted synchronously from that.
|
14 years ago |
|
Con Kolivas
|
2b6e841673
Use a buffer of up to 512 * 4 integers when retrieving work from the GPU.
|
14 years ago |
|
ckolivas
|
6af84770d0
Add spaces to make output clearer.
|
14 years ago |
|
ckolivas
|
e1dd27c5c2
Ensure that we don't overflow due to 32 bit limitations.
|
14 years ago |
|
ckolivas
|
b38a02bd24
Make the log time hash rate a rolling exponential average so it doesn't fluctuate so dramatically.
|
14 years ago |
|
ckolivas
|
08a7821072
Make the log show what the thread is: cpu or gpu and what number.
|
14 years ago |
|
ckolivas
|
f490143a9a
Add local thread count to info, store hw error count, and make share submission debug only.
|
14 years ago |
