Then it should be fairly trivial to call cgo to raise the priority of the ‘audio thread/routine after call runtime,LockOSthread() - nice !
> On Sep 17, 2018, at 1:36 PM, Ian Lance Taylor <i...@golang.org> wrote: > > On Mon, Sep 17, 2018 at 10:39 AM, Scott Cotton <w...@iri-labs.com> wrote: >> >> Wanted to ask about the Go runtime use of threads. Specifically, suppose >> I've got an app in mind that would run OS-priveleged and use specially >> scheduled threads, like SCHED_RR in linux for example. >> >> One could do this with chrt or calling from a process/thread at the desired >> scheduling priority/type (as pointed out on a related thread in golang-dev) >> >> The question is: does this as of go1.11 interfere with Go runtime internal >> prioritising of threads? >> The other question is: may it one day interfere with Go runtime internal >> prioritising of threads? > > Using specially scheduled threads should not be a problem if the Go > code that runs on those threads reliably calls runtime.LockOSThread. > If not, then it's hard to say. > > Ian > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
