On 2017-03-22 09:10:03 [-0400], Brian Wrenn wrote: > Hi Julia (and anyone else following), > > I was looking at that exact page yesterday. W.r.t. the sample code on > the wiki, I'd need to address five function calls. Here's what I > found. > > // ::boost::thread provides it's own ::boost::thread::attributes, but > it's not as > // comprehensive, i.e. only includes stack size. ::std::thread at > this point aims to > // be cross platform and hence doesn't. pthread_attr_setstack() is defined in POSIX so depending on how cross platform you aim to be, it could be adde… > // Finding: ::boost::thread==>kinda, ::std::thread==>no > pthread_attr_init(&attr); > > // Can apply to ::boost::thread via ::boost::thread::attributes, but > not ::std::thread. > // Finding: same as previous > pthread_attr_setstack(&attr, stack_buf, PTHREAD_STACK_MIN); > > // Can only apply at the attribute level prior to creating, at least > with the pthread > // API I have for arm64, a therefore not via native_handle(). > // Finding: ::boost::thread==>no, ::std::thread==>no > pthread_attr_setschedpolicy(&attr, SCHED_FIFO); > > // Can apply via native_handle(). > // Finding: ::boost::thread==>yes, ::std::thread==>yes > pthread_attr_setschedparam(&attr, ¶m); > > // Can only apply at the attribute level and not via native_handle(). > // Finding: ::boost::thread==>no, ::std::thread==>no > pthread_attr_setinheritsched(&attr, PTHREAD_EXPLICIT_SCHED); > > If there's some way to use pthread_self() to address the calls that > can't work on native_handle(), I haven't found it yet. > > Alternatively, if I were to use sched_setscheduler() instead of > pthread attributes, that eliminates three of the above, which means > one could conceivably use ::boost::thread and > ::boost::thread::attributes to set the stacksize, but to cross compile > the boost libraries, as I'd need to link against boost_system.so/a, it > may not be worth the effort over just using pthreads. So if you I get you right, you can't use std::thread or boost because each one lacks some support you want to have. The best thing you get is boost which lacks a wrapper around pthread_setschedparam(), is that so? Because from google most people suggest to use pthread_setschedparam(tread.native_handle, ¶m); and if that is the case, you could ask the boost folks to get native support for it, since this is posix. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
