Re: Proposed new TS API function: TSContScheduleOnEntirePool

2023-11-10 Thread Fei Deng
Updating the API prototypes a little here to reflect the changes done in the PR. std::vector TSContScheduleOnEntirePool(TSCont contp, TSHRTime timeout, TSThreadPool tp) std::vector TSContScheduleEveryOnEntirePool(TSCont contp, TSHRTime every, TSThreadPool tp) TSContScheduleOnEntirePool() is used

Re: Proposed new TS API function: TSContScheduleOnEntirePool

2023-10-20 Thread Leif Hedstrom
We would need something to allow for one shot calls (eg initializing some thread local data). — Leif > On Oct 20, 2023, at 09:11, Fei Deng wrote: > > We should be able to make it behave like that. But the current > schedule_every has an assert for (t != 0). > >> On Tue, Oct 17, 2023 at 10:0

Re: Proposed new TS API function: TSContScheduleOnEntirePool

2023-10-20 Thread Fei Deng
We should be able to make it behave like that. But the current schedule_every has an assert for (t != 0). On Tue, Oct 17, 2023 at 10:09 AM Leif Hedstrom wrote: > I assume “every” can be zero for a one time shot on every thread of the > specified type? > > — Leif > > > On Oct 17, 2023, at 07:26,

Re: Proposed new TS API function: TSContScheduleOnEntirePool

2023-10-17 Thread Leif Hedstrom
I assume “every” can be zero for a one time shot on every thread of the specified type? — Leif > On Oct 17, 2023, at 07:26, Fei Deng wrote: > > tsapi::c::TSAction > tsapi::c::TSContScheduleEveryOnEntirePool(TSCont contp, TSHRTime every, > TSThreadPool tp); > > With this we can schedule a co