The Intel IXP Microengine (Now Netronome?) architecture supported this explicitly. You could schedule a memory read explicitly, do other things, then come back. Each core was also 8-way multi-threaded, and you could yield explicitly to the next thread.
The question of whether LibreSSL has fixes for OpenSSL issues comes up frequently enough that it made sense to note it directly.
Fixes and improvements have certainly been shared between the Boring, Open and LibreSSL teams, and we look forward to further cooperation. It is obviously beneficial.
LibreSSL has in the past mitigated issues that later became known in OpenSSL through security updates. Sometimes, it has been still vulnerable to OpenSSL issues as well. Hopefully we'll fall into the former camp this time around.
To the security researchers and developers who have reached out, we are very grateful.
Development slowed approaching the end of 2.1.x as the OpenBSD tree went in release mode lockdown. It is interesting to see the development coordination that stops and restarts the tree activity.
Things in the pipeline for 2.2.x include AIX, Cygwin, Visual Studio support, and wider support for optimizations (currently only ELF/OS X x64 is supported). In general, expect libtls to expand in features and improve usability, more code to be pruned and simplified.
There were not many SSL patches for OpenBSD 5.6, and there were not any LibreSSL 2.0.x releases after 2.1.x began. However, we are looking at possibly releasing further 2.1.x updates if there is interest. They would correspond to OpenBSD 5.7 errata.
If you don't mind elaborating a bit more on the troubles you had, I might be able to help get things fixed for a later release.
I have had some trouble on Solaris getting the adjtime olddelta value to settle quickly, but haven't heard of any other issues. Even if you're happy with clockspeed, it might help other users to identify the problem.