masayuki2009 commented on issue #11567:
URL: https://github.com/apache/nuttx/issues/11567#issuecomment-1902945782
@acassis
> @masayuki2009 since you did many improvements over original SMP, maybe you
can have some suggestion to help here.
I think @tmedicci's comments are correct.
acassis commented on issue #11567:
URL: https://github.com/apache/nuttx/issues/11567#issuecomment-1902413399
@masayuki2009 since you did many improvements over original SMP, maybe you
can have some suggestion to help here.
--
This is an automated message from the Apache Git Service.
To
w2016561536 commented on issue #11567:
URL: https://github.com/apache/nuttx/issues/11567#issuecomment-190096
> > In picture 1, wq:rate_ctrl take up all the cpu resources. But actually,
it does not run, just stuck there. It look like cpu 0 is dead
>
> The picture does not show
tmedicci commented on issue #11567:
URL: https://github.com/apache/nuttx/issues/11567#issuecomment-1900914400
> In picture 1, wq:rate_ctrl take up all the cpu resources. But actually, it
does not run, just stuck there. It look like cpu 0 is dead
The picture does not show that. It
w2016561536 commented on issue #11567:
URL: https://github.com/apache/nuttx/issues/11567#issuecomment-1900887696
In picture 1, wq:rate_ctrl take up all the cpu resources. But actually, it
does not run, just stuck there. It look like cpu 0 is dead
--
This is an automated message from the
tmedicci commented on issue #11567:
URL: https://github.com/apache/nuttx/issues/11567#issuecomment-1900842862
HI @w2016561536 !
I didn't get exactly what is your problem, but I saw no problems regarding
your process scheduling in the images you shared. Could you please elaborate
w2016561536 opened a new issue, #11567:
URL: https://github.com/apache/nuttx/issues/11567
At first, thank you for reading this issue. I'm not quite sure if it
occurred by NuttX scheduling. Perhaps applications cause this issue.
