13:34 <Yorlik> heller: yt

13:35 <Yorlik> When I checked the doc links you sent yesterday, I realized some of the links inside these docs were defunct.

13:35 <Yorlik> In the fibonacci example

14:08 <heller> Yorlik: yeah, no idea why

14:12 <Yorlik> Unrelated question: I am trying to abstract away the differences in my Disruptor between running under HPX or vanilla. This means for example, that in spinning loops I use either this_thread::sleep:for or hpx::this_thread::yield. What would be the best way to abstract this? CRTP Mixins? To me it resembles from what I heared about executors or execution contexts. Ideas?

15:36 <Yorlik> How fast in an order of magnitude are hpx context switches ?

15:37 <Yorlik> Especially a hpx::this_thread::yield( ) roundtrip?

15:57 <hkaiser> Yorlik: sub-microseconds

15:58 <Yorlik> Allright. Thanks.

15:58 <hkaiser> Yorlik: for the abstraction: use executors and write your own for std::threads

15:58 <Yorlik> I am currently thinking about these things. I call the execution contexts, but maybe that's not good terminology.

15:59 <Yorlik> I am plaing with things like this:

15:59 <Yorlik> struct hpx_execution_context : public iExecutionContext {

15:59 <Yorlik> void generic_wait_us( uint32_t wait_us ) {

15:59 <Yorlik> /// @todo: make hard coded threshold of 200 us configurable

15:59 <Yorlik> /// A task being swapped in would probably run at least ~200 us

15:59 <Yorlik> /// so - any wait being smaller is not really worth to yield.

15:59 <Yorlik> /// Using a yield() roundtrip time might be

15:59 <Yorlik> /// also OK (and a shorter interval)

15:59 <Yorlik> if ( wait_us < 200 ) {

15:59 <Yorlik> hpx::this_thread::sleep_for(

15:59 <Yorlik> std::chrono::microseconds( wait_us ) );

15:59 <Yorlik> }

15:59 <Yorlik> else {

15:59 <Yorlik> hpx::this_thread::yield( );

15:59 <Yorlik> }

15:59 <Yorlik> }

15:59 <Yorlik> ---

16:00 <hkaiser> shrug, sure

16:00 <Yorlik> i am thinking about making these contexts CRTPed mix-ins, so i can keep it independent from HPX or any other threaded runtime environment. I coul e.g. extend it to coroutines or fibers later

16:01 <Yorlik> Why shrug?

20:25 <heller> Yorlik: Look at my execution_context branch, it has exactly this

20:26 <heller> Using runtime polymorphism