Re: RFC: make _fiber_start() return a handle on the fiber
Liu, Sharron <sharron.liu@...>
Returning a handler maybe is good for app to invoke other fiber related APIs for operation on same fiber.
toggle quoted messageShow quoted text
But regarding the case described below, I have question can "nano_sem_give" be used instead of requesting fiber_wakeup()? From Zephyr document I learnt both "semaphore wait" and "sleep" blocks the execution of fiber and triggers the scheduler to dequeue another executable fiber. Thanks, Sharron
-----Original Message-----
From: Benjamin Walsh [mailto:benjamin.walsh(a)windriver.com] Sent: Saturday, February 20, 2016 1:17 AM To: Nashif, Anas <anas.nashif(a)intel.com> Cc: devel(a)lists.zephyrproject.org; Rissanen, Jukka <jukka.rissanen(a)intel.com> Subject: [devel] Re: RFC: make _fiber_start() return a handle on the fiber Sure.You are right, this will not break existing code. Nevertheless, weWe're just returning a thread ID when we start a fiber now, you canWhen we start a fiber via the _fiber_start() API family, we don'tSounds good, but we need to do it in away that keeps APIs
|
|