Using Micro-XRCE. DDS over Ethernet Performance analysis The output of the performance benchmarking tools is shown below: file: /uros_ws/firmware/NuttX/sched/init/nx_start.c function: nx_start hits: 618 details: [ { hits: 311, line: 876, address: 8001120}, { hits: 307, line: 876, address: 8001124}, ] file: /uros_ws/firmware/NuttX/arch/arm/src/chip/stm32_idle.c function: up_idle hits: 311 details: [ { hits: 311, line: 433, address: 80039fc}, ] file: /uros_ws/firmware/NuttX/arch/arm/src/chip/stm32_eth.c function: stm32_phyread hits: 618 details: [ { hits: 2, line: 2980, address: 80056a8}, { hits: 1, line: 2986, address: 80056aa}, { hits: 1, line: 2987, address: 80056b4}, { hits: 1, line: 2993, address: 80056c0}, { hits: 1, line: 2997, address: 80056c6}, { hits: 1, line: 3001, address: 80056ca}, { hits: 58, line: 3001, address: 80056cc}, { hits: 34, line: 3001, address: 80056ce}, { hits: 68, line: 3001, address: 80056d0}, { hits: 163, line: 3003, address: 80056d8}, { hits: 31, line: 3003, address: 80056da}, { hits: 68, line: 3003, address: 80056de}, { hits: 1, line: 3005, address: 80056e2}, { hits: 1, line: 3005, address: 80056e4}, { hits: 1, line: 3014, address: 80056e8}, { hits: 57, line: 3001, address: 80056ea}, { hits: 33, line: 3001, address: 80056ec}, { hits: 32, line: 3001, address: 80056ee}, { hits: 64, line: 3001, address: 80056f0}, ] Observations and analysis: Below the code’s snippets that are refered by the tool: • /uros_ws/firmware/NuttX/sched/init/nx_start.c:876: 842 /* The IDLE Loop **********************************************************/ 843 /* When control is return to this point, the system is idle. */ 844 845 sinfo("CPU0: Beginning Idle Loop\n"); 846 for (; ; ) 847 { 848 /* Perform garbage collection (if it is not being done by the worker 849 * thread). This cleans-up memory de-allocations that were queued 850 * because they could not be freed in that execution context (for 851 * example, if the memory was freed from an interrupt handler). 852 */ 853 854 #ifndef CONFIG_SCHED_WORKQUEUE 855 /* We must have exclusive access to the memory manager to do this 856 * BUT the idle task cannot wait on a semaphore. So we only do 857 * the cleanup now if we can get the semaphore -- this should be 858 * possible because if the IDLE thread is running, no other task is! 859 * 860 * WARNING: This logic could have undesirable side-effects if priority 861 * inheritance is enabled. Imaginee the possible issues if the 862 * priority of the IDLE thread were to get boosted! M...
