Con Kolivas
|
3267b534a8
Implement rudimentary X-Mining-Hashrate support.
|
13 years ago |
Con Kolivas
|
4c5d41a8dd
Merge pull request #243 from kanoi/master
|
13 years ago |
Con Kolivas
|
24316fc7fc
Revert "Work is checked if it's stale elsewhere outside of can_roll so there is no need to check it again."
|
13 years ago |
Con Kolivas
|
5ad58f9a5c
Work is checked if it's stale elsewhere outside of can_roll so there is no need to check it again.
|
13 years ago |
Con Kolivas
|
eddd02fea1
Put upper bounds to under 2 hours that work can be rolled into the future for bitcoind will deem it invalid beyond that.
|
13 years ago |
Con Kolivas
|
bcec5f5102
Revert "Check we don't exhaust the entire unsigned 32 bit ntime range when rolling time to cope with extremely high hashrates."
|
13 years ago |
Con Kolivas
|
383d35b221
Merge branch 'master' of github.com:ckolivas/cgminer
|
13 years ago |
Con Kolivas
|
522f620c89
Check we don't exhaust the entire unsigned 32 bit ntime range when rolling time to cope with extremely high hashrates.
|
13 years ago |
Kano
|
c21fc06560
define API option --api-groups
|
13 years ago |
ckolivas
|
794b6558a3
Merge branch 'master' of https://github.com/ckolivas/cgminer
|
13 years ago |
ckolivas
|
21a23a45d7
Work around pools that advertise very low expire= time inappropriately as this leads to many false positives for stale shares detected.
|
13 years ago |
Con Kolivas
|
68a3a9ad10
There is no need for work to be a union in struct workio_cmd
|
13 years ago |
ckolivas
|
b198423d17
Don't keep rolling work right up to the expire= cut off. Use 2/3 of the time between the scantime and the expiry as cutoff for reusing work.
|
13 years ago |
ckolivas
|
6e80b63bb8
Revert "Increase the getwork delay factored in to determine if work vs share is stale to avoid too tight timing."
|
13 years ago |
ckolivas
|
d8de1bbc5b
Increase the getwork delay factored in to determine if work vs share is stale to avoid too tight timing.
|
13 years ago |
Con Kolivas
|
c027492fa4
Make the pools array a dynamically allocated array to allow unlimited pools to be added.
|
13 years ago |
Con Kolivas
|
5cf4b7c432
Make the devices array a dynamically allocated array of pointers to allow unlimited devices.
|
13 years ago |
Con Kolivas
|
17ba2dca63
Logic fail on queueing multiple requests at once. Just queue one at a time.
|
13 years ago |
Con Kolivas
|
42ea29ca4e
Use a queueing bool set under control_lock to prevent multiple calls to queue_request racing.
|
13 years ago |
Con Kolivas
|
63dd598e2a
Queue multiple requests at once when levels are low.
|
13 years ago |
Con Kolivas
|
757922e4ce
Use the work clone flag to determine if we should subtract it from the total queued variable and provide a subtract queued function to prevent looping over locked code.
|
13 years ago |
Con Kolivas
|
49dd8fb548
Don't decrement staged extras count from longpoll work.
|
13 years ago |
Con Kolivas
|
d93e5f710d
Count longpoll's contribution to the queue.
|
13 years ago |
Con Kolivas
|
05bc638d97
Increase queued count before pushing message.
|
13 years ago |
Con Kolivas
|
32f5272123
Revert "With better bounds on the amount of work cloned, there is no need to age work and ageing it was picking off master work items that could be further rolled."
|
13 years ago |
Con Kolivas
|
5d90c50fc0
With better bounds on the amount of work cloned, there is no need to age work and ageing it was picking off master work items that could be further rolled.
|
13 years ago |
Con Kolivas
|
47f66405c0
Alternatively check staged work count for rolltime capable pools when deciding to queue requests.
|
13 years ago |
Con Kolivas
|
efa9569b66
Test we have enough work queued for pools with and without rolltime capability.
|
13 years ago |
Con Kolivas
|
1bbc860a15
Don't count longpoll work as a staged extra work.
|
13 years ago |
Con Kolivas
|
ebaa615f6d
Count extra cloned work in the total queued count.
|
13 years ago |