27 Commits (ebd2142114a46d10ad002223fac4c491f008fce0)

Author	SHA1	Message	Date
Jason Rhinelander	ebd2142114	Don't use std::optional::value() because f u macos ... This replaces all use of std::optional's `opt.value()` with `*opt` because macOS is great and the ghost of Steve Jobs says that actually supporting std::optional's value() method is not for chumps before macOS 10.14. So don't use it because Apple is great. Pretty much all of our use of it actually is done better with operator* anyway (since operator* doesn't do a check that the optional has a value). Also replaced *most* of the `has_value()` calls with direct bool context, except for one in the config section which looked really confusing at a glance without a has_value().	4 years ago
Stephen Shelton	273270916e	The Great Wall of Blame ... This commit reflects changes to clang-format rules. Unfortunately, these rule changes create a massive change to the codebase, which causes an apparent rewrite of git history. Git blame's --ignore-rev flag can be used to ignore this commit when attempting to `git blame` some code.	4 years ago
Jason Rhinelander	b4440094b0	De-abseil, part 2: mutex, locks, (most) time ... - util::Mutex is now a std::shared_timed_mutex, which is capable of exclusive and shared locks. - util::Lock is still present as a std::lock_guard<util::Mutex>. - the locking annotations are preserved, but updated to the latest supported by clang rather than using abseil's older/deprecated ones. - ACQUIRE_LOCK macro is gone since we don't pass mutexes by pointer into locks anymore (WTF abseil). - ReleasableLock is gone. Instead there are now some llarp::util helper methods to obtain unique and/or shared locks: - `auto lock = util::unique_lock(mutex);` gets an RAII-but-also unlockable object (std::unique_lock<T>, with T inferred from `mutex`). - `auto lock = util::shared_lock(mutex);` gets an RAII shared (i.e. "reader") lock of the mutex. - `auto lock = util::unique_locks(mutex1, mutex2, mutex3);` can be used to atomically lock multiple mutexes at once (returning a tuple of the locks). This are templated on the mutex which makes them a bit more flexible than using a concrete type: they can be used for any type of lockable mutex, not only util::Mutex. (Some of the code here uses them for getting locks around a std::mutex). Until C++17, using the RAII types is painfully verbose: ```C++ // pre-C++17 - needing to figure out the mutex type here is annoying: std::unique_lock<util::Mutex> lock(mutex); // pre-C++17 and even more verbose (but at least the type isn't needed): std::unique_lock<decltype(mutex)> lock(mutex); // our compromise: auto lock = util::unique_lock(mutex); // C++17: std::unique_lock lock(mutex); ``` All of these functions will also warn (under gcc or clang) if you discard the return value. You can also do fancy things like `auto l = util::unique_lock(mutex, std::adopt_lock)` (which lets a lock take over an already-locked mutex). - metrics code is gone, which also removes a big pile of code that was only used by metrics: - llarp::util::Scheduler - llarp:🧵:TimerQueue - llarp::util::Stopwatch	4 years ago
Thomas Winget	f4c9e09d44	remove obsolete timer-related code	5 years ago
Thomas Winget	71bb0dd520	implement timers using libuv ... So far only a bit of the code using timers has been modified to use the new libuv-based timers. Also only the non-Windows case has been implemented. Seems to be working though, so it's a good time to commit.	5 years ago
Jeff Becker	8455d5d1cf	more cleanup	5 years ago
Jeff Becker	b286230d40	limit timer calls	5 years ago
Jeff Becker	35672e6d8c	call timers with queuer if set	5 years ago
Jeff Becker	cec36b62b5	make logic and net thread one in the same	5 years ago
Jeff Becker	7d5fd132c8	make format	5 years ago
Jeff Becker	3c85691f81	limit calls to pumpll such that it gets called fast enough but not too much under load	5 years ago
Jason Rhinelander	740460318a	Die if job queue full ... If this happens it's a pretty serious error; if someone is hitting it occassionally it's better to know and update their queue size (and if it is a runaway situation lokinet doesn't come back anyway).	5 years ago
Jeff Becker	fba1e47d1c	call jobs in logic	5 years ago
Jeff Becker	a3a62c34f3	use timer guard for all jobs in debug mode	5 years ago
Jeff Becker	11d4760c3d	add metrics tracking for logic jobs in debug mode	5 years ago
Jeff Becker	dd48b149ca	make job queue size configurable	5 years ago
Jeff Becker	56dce90de9	add trace log level for tracking logic thread jobs	5 years ago
Jeff Becker	eb6d042e73	make sure all calls of logic thread jobs are not having contention	5 years ago
Jeff Becker	168d25f244	add warning when trying to queue onto full logic thread	5 years ago
Jeff Becker	f16c9f9b5d	iot seems that logic thread didn't work the way i remember it should ... make logic work the way it should	5 years ago
Jeff Becker	3c8e148372	prevent double free crap with shared_ptr	5 years ago
jeff	605da68e15	use absl optional	5 years ago
Jeff Becker	327c545530	finish multithread cryptography first pass	5 years ago
jeff	14c9ef15ed	try calling stuff in logic thread from event loop	5 years ago
jeff	ac2a2aed1d	gut libutp and finish making things compile and pass tests	5 years ago
Jeff Becker	e3bb59707e	more	5 years ago
Michael	edd0ec398f	Move thread stuff to subdirectory	5 years ago