masayuki2009 commented on PR #7920:
URL: https://github.com/apache/nuttx/pull/7920#issuecomment-1357296625

   @anchao 
   
   I noticed that `iperf -s` performance with `qemu-armv8a:netnsh_smp` is not 
so good compared to the latest upstream.
   
   Latest upstream:
   
   ```
   nsh> uname -a
   uname -a
   NuttX  12.0.0 6e66603da5 Dec 19 2022 17:30:16 arm64 qemu-armv8a
   nsh> ps
   ps
     PID GROUP CPU PRI POLICY   TYPE    NPX STATE    EVENT     SIGMASK   STACK  
 USED  FILLED COMMAND
       0     0   0   0 FIFO     Kthread N-- Running            00000000 008144 
001040  12.7%  CPU0 IDLE
       1     1   1   0 FIFO     Kthread N-- Assigned           00000000 008144 
000320   3.9%  CPU1 IDLE
       2     2   2   0 FIFO     Kthread N-- Running            00000000 008144 
000320   3.9%  CPU2 IDLE
       3     3   3   0 FIFO     Kthread N-- Running            00000000 008144 
000080   0.9%  CPU3 IDLE
       4     4 --- 192 RR       Kthread --- Waiting  Semaphore 00000000 008096 
000496   6.1%  hpwork 0x402d65d8
       5     5 --- 100 RR       Kthread --- Waiting  Semaphore 00000000 008096 
001184  14.6%  lpwork 0x402d6608
       6     6 --- 100 RR       Task    --- Waiting  Semaphore 00000000 008112 
002288  28.2%  nsh_main
       7     7 --- 100 RR       Task    --- Waiting  Semaphore 00000010 008112 
001392  17.1%  telnetd
      10    10   1 100 RR       Task    --- Running            00000010 008112 
002720  33.5%  Telnet session
   nsh> iperf -s -i 1
          IP: 10.0.2.15
   
    mode=tcp-server sip=10.0.2.15:5001,dip=0.0.0.0:5001, interval=1, time=0
   accept: 10.0.2.2,38568
   
              Interval         Transfer         Bandwidth
   
      0.00-   1.01 sec   35423544 Bytes  280.20 Mbits/sec
      1.01-   2.02 sec   37002240 Bytes  293.07 Mbits/sec
      2.02-   3.03 sec   36266400 Bytes  287.13 Mbits/sec
      3.03-   4.04 sec   36873760 Bytes  291.09 Mbits/sec
      4.04-   5.05 sec   37142400 Bytes  294.06 Mbits/sec
   closed by the peer: 10.0.2.2,38568
   ```
   
   This PR:
   
   ```
   nsh> uname -a
   uname -a
   NuttX  10.4.0 f4c530da3e Dec 19 2022 17:37:34 arm64 qemu-armv8a
   nsh> ps
   ps
     PID GROUP CPU PRI POLICY   TYPE    NPX STATE    EVENT     SIGMASK   STACK  
 USED  FILLED COMMAND
       0     0   0   0 FIFO     Kthread N-- Running            00000000 008144 
001040  12.7%  CPU0 IDLE
       1     1   1   0 FIFO     Kthread N-- Assigned           00000000 008144 
000320   3.9%  CPU1 IDLE
       2     2   2   0 FIFO     Kthread N-- Running            00000000 008144 
000320   3.9%  CPU2 IDLE
       3     3   3   0 FIFO     Kthread N-- Running            00000000 008144 
000080   0.9%  CPU3 IDLE
       4     4 --- 192 RR       Kthread --- Waiting  Semaphore 00000000 008096 
000496   6.1%  hpwork 0x402d65d8
       5     5 --- 100 RR       Kthread --- Waiting  Semaphore 00000000 008096 
001184  14.6%  lpwork 0x402d6608
       6     6 --- 100 RR       Task    --- Waiting  Semaphore 00000000 008112 
002368  29.1%  nsh_main
       7     7 --- 100 RR       Task    --- Waiting  Semaphore 00000010 008112 
001392  17.1%  telnetd
       8     8   1 100 RR       Task    --- Running            00000010 008112 
002720  33.5%  Telnet session
   nsh> iperf -s -i 1
          IP: 10.0.2.15
   
    mode=tcp-server sip=10.0.2.15:5001,dip=0.0.0.0:5001, interval=1, time=0
   accept: 10.0.2.2,56102
   
              Interval         Transfer         Bandwidth
   
      0.00-   1.01 sec   25520364 Bytes  201.98 Mbits/sec
      1.01-   2.02 sec   26209920 Bytes  206.93 Mbits/sec
      2.02-   3.03 sec   24025760 Bytes  190.10 Mbits/sec
      3.03-   4.04 sec   22997920 Bytes  181.19 Mbits/sec
      4.04-   5.05 sec   22530720 Bytes  178.22 Mbits/sec
   closed by the peer: 10.0.2.2,56102
   ```


-- 
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

Reply via email to