Luke Dashjr
06023e549e
Bugfix: Return failure, rather than quit, if BFwrite fails
13 years ago
Luke Dashjr
4ba9006d0e
Disable failing devices such that the user can attempt to re-enable them
13 years ago
Luke Dashjr
124ee9b28a
Bugfix: thread_shutdown shouldn't try to free the device, since it's needed afterward
13 years ago
Kano
afa3fa56b6
API bool's and 1TBS fixes
13 years ago
Kano
09fe8bcb12
Icarus - minimise code delays and name timer variables
13 years ago
Kano
524e2fb8f2
api.c V1.9 add 'restart' + redesign 'quit' so thread exits cleanly
13 years ago
Kano
01c93bc1d4
api.c bug - remove extra ']'s in notify command
13 years ago
ckolivas
5cf4e188fd
Increase pool watch interval to 30 seconds.
13 years ago
ckolivas
85008a7853
Reap curls that are unused for over a minute.
...
This allows connections to be closed, thereby allowing the number of curl handles to always be the minimum necessary to not delay networking.
13 years ago
Con Kolivas
ec3d057016
Use the ringbuffer of curls from the same pool for submit as well as getwork threads.
...
Since the curl handles were already connected to the same pool and are immediately available, share submission will not be delayed by getworks.
13 years ago
Con Kolivas
7d288eac9f
Implement a scaleable networking framework designed to cope with any sized network requirements, yet minimise the number of connections being reoped.
...
Do this by create a ring buffer linked list of curl handles to be used by getwork, recruiting extra handles when none is immediately available.
13 years ago
nelisky
57a72d51fb
Blind implementation of multi-fpga board 1.15y.
13 years ago
Con Kolivas
89053c78da
There is no need for the submit and getwork curls to be tied to the pool struct.
13 years ago
ckolivas
adda6e6680
Do not recruit extra connection threads if there have been connection errors to the pool in question.
13 years ago
ckolivas
7638511290
We should not retry submitting shares indefinitely or we may end up with a huge backlog during network outages, so discard stale shares if we failed to submit them and they've become stale in the interim.
13 years ago
nelisky
719b0c7cee
HS bitstream configuration
13 years ago
Con Kolivas
0171c84e75
Bump version number to 2.3.6
13 years ago
Con Kolivas
e8eeea4cfc
More NEWS.
13 years ago
Con Kolivas
b015348df4
Shorten stale share messages slightly.
13 years ago
Con Kolivas
7233890d85
Protect the freeing of current_hash under mutex_lock to prevent racing on it when set_curblock is hit concurrently.
13 years ago
Con Kolivas
10f619cb2f
Update NEWS.
13 years ago
Con Kolivas
53c22551f7
Change default behaviour to submitting stale, removing the --submit-stale option and adding a --no-submit-stale option.
13 years ago
Con Kolivas
f9123f0587
Make sure to start the getwork and submit threads when a pool is added on the fly.
13 years ago
Con Kolivas
5ad942d187
Faster hardware can easily outstrip the speed we can get work and submit shares when using only one connection per pool.
...
Test the queued list to see if any get/submits are already queued and if they are, start recruiting extra connections by generating new threads.
This allows us to reuse network connections at low loads but recuit new open connections as they're needed, so that cgminer can scale to hardware of any size.
13 years ago
Con Kolivas
60cc425ff8
Bump version number to 2.3.5
13 years ago
Con Kolivas
628ac19977
Get rid of confusing "waiting on fresh work" part of longpoll message to minimise log width and add pool number to longpoll work restart message.
13 years ago
Con Kolivas
06bf44b06f
Restarting cgminer leads to a socket that can't be bound for 60 seconds, so increase the interval that API binding waits to 30 seconds to minimise the number of times it will retry, spamming the logs.
13 years ago
Con Kolivas
972860c0af
Remove unused variable.
13 years ago
Con Kolivas
3362a2a447
Give a longpoll message for any longpoll that detects a block change, primary or backup, and also display which pool it was.
13 years ago
Con Kolivas
e1cf5029d4
Decrease utility display to one decimal place.
13 years ago
Con Kolivas
e5ae415f80
News updates.
13 years ago
Con Kolivas
7b370bb2e7
Small cosmetic output alignment.
13 years ago
Con Kolivas
669b0deda3
Add pool number to stale share message.
13 years ago
Con Kolivas
4da6758f43
Add space to log output now that there is more screen real estate available.
13 years ago
Con Kolivas
268039cc7e
Indentation clean up.
13 years ago
Con Kolivas
30755adcff
Merge branch 'master' of github.com:ckolivas/cgminer
13 years ago
Con Kolivas
03fab3f438
Remove thread id display from rejected shares as well.
13 years ago
Con Kolivas
5d99f5d3e8
Merge pull request #185 from Diapolo/diakgcn
...
add goffset support for diakgcn with -v 1 and update kernel version
13 years ago
Philip Kaufmann
f479be0700
add goffset support for diakgcn with -v 1 and update kernel version
13 years ago
Con Kolivas
86e94edb89
Set have_longpoll to true when there is at least one pool with longpoll.
13 years ago
Con Kolivas
0365878ac5
Don't display the thread ID since it adds no useful information over the device number.
13 years ago
Con Kolivas
08c721080d
Don't display the first 8 bytes of a share since they will always be zero at >= 1 difficulty.
13 years ago
Con Kolivas
501e35a0e6
work->longpoll is reset across test_work_current so we need to recheck what pool it belongs to.
13 years ago
Con Kolivas
03abb70467
Use longpolls from backup pools with failover-only enabled just to check for block changes, but don't use them as work.
13 years ago
Con Kolivas
1ab318d0f3
Start longpoll only after we have tried to extract the longpoll URL.
13 years ago
Con Kolivas
b1c273e71b
Check for submitold flag on resubmit of shares, and give different message for stale shares on retry.
13 years ago
Con Kolivas
5ece966f07
Check for submitold before submitstale.
13 years ago
Con Kolivas
ed718b2b50
Don't force fresh curl connections on anything but longpoll threads.
13 years ago
Con Kolivas
eda382990a
Create one longpoll thread per pool, using backup pools for those pools that don't have longpoll.
...
Use the work created from the longpoll return only if we don't have failover-enabled, and only flag the work as a longpoll if it is the current pool.
This will work around the problem of trying to restart the single longpoll thread on pool changes that was leading to race conditions.
It will also have less work restarts from the multiple longpolls received from different pools.
13 years ago
Con Kolivas
e502fde52b
Remove the ability to disable longpoll. It is not a useful feature and will conflict with planned changes to longpoll code.
13 years ago