| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Readd copyright starting date | xmr-eric | 2018-01-26 | 1 | -1/+1 |
| | | |||||
| * | Update 2018 copyright | xmr-eric | 2018-01-26 | 1 | -1/+1 |
| | | |||||
| * | threadpool: fix deadlock in recursive waiter usage | moneromooo-monero | 2017-12-23 | 1 | -1/+7 |
| | | | | | | | | | | | If a queued job uses a waiter, then we want to run that waiter's jobs in the current thread if all threads are busy, even if the queue is empty, since there is no guarantee that any thread will free up to take care of that new job, since all the threads might be running a job which spawns such a recursive job and will block till that recursive job is done, which it will never be since it relies on the queue being polled by one of those blocked threads. | ||||
| * | Use max_concurrency as-is | Howard Chu | 2017-11-02 | 1 | -2/+2 |
| | | | | | Don't try to 2nd guess user | ||||
| * | Tweak concurrency limits | Howard Chu | 2017-09-15 | 1 | -1/+5 |
| | | | | | Create capacity for 2x max, but lie about it | ||||
| * | Use a threadpool | Howard Chu | 2017-09-14 | 1 | -0/+113 |
| Instead of constantly creating and destroying threads | |||||
 |
index : monzero-core.git | |
| Monzero core node, command-line wallet, consensus code, and release tooling. | www-data |
| aboutsummaryrefslogtreecommitdiff |