hujun260 commented on PR #16673: URL: https://github.com/apache/nuttx/pull/16673#issuecomment-3095103424
> Doesn't this actually simplify it a lot? It is basically removing a lot of redundant paths for scheduling between smp cores. > > I only measured the overall performance on a system with several tasks processing data with high frequency, and see no change. > > Do you have some specific tool in mind, to measure the context switching performance? > > I'll try to make this smaller by keeping rr out of it, sometime next week! Take the frequently called nxsched_add_readytorun/nxsched_process_delivered as examples. Before your modification: If a context switch occurs on the current CPU, there is no need to call any loop function. If a context switch occurs on another CPU, the loop operation only needs to be called once. After your modification: At least two or three loop functions need to be called. As for performance evaluation, it is actually not too difficult. For example, there are 2 tasks, in two cases: on the same core or on different cores. For instance, taskB is "waiting", and taskA initiates a "post" operation. We need to calculate the time from when taskA initiates the operation to when taskB is awakened. You can refer to the screenshots below <img width="1203" height="638" alt="image" src="https://github.com/user-attachments/assets/d3da0394-49fc-440f-8002-7568fac67dd2"; /> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
