Greg, The debugging output is great! Thanks. I'll try that on the SAMA5D36 too. With CONFIG_SIM_WALLTIME=y the loopback tcpblaster seems to chunk along pretty quickly: Sent 50 buffers: 200.0 Kb (avg 4.0 Kb) in 7823.46 Sec ( 0.0 Kb/Sec) Received 50 buffers: 66.6 Kb (avg 1.3 Kb) in 2575.50 Sec ( 0.0 Kb/Sec) Received 50 buffers: 66.9 Kb (avg 1.3 Kb) in 2575.50 Sec ( 0.0 Kb/Sec) Received 50 buffers: 66.6 Kb (avg 1.3 Kb) in 2575.50 Sec ( 0.0 Kb/Sec) Sent 50 buffers: 200.0 Kb (avg 4.0 Kb) in 7665.90 Sec ( 0.0 Kb/Sec) Received 50 buffers: 66.6 Kb (avg 1.3 Kb) in 2499.75 Sec ( 0.0 Kb/Sec) Received 50 buffers: 66.9 Kb (avg 1.3 Kb) in 2424.00 Sec ( 0.0 Kb/Sec) Received 50 buffers: 66.6 Kb (avg 1.3 Kb) in 2424.00 Sec ( 0.0 Kb/Sec)
So it appears to be working fine in the simulator. Now if I could get the simulator to network with the linux host, I could test out non-loopback mode. I am still not sure what's wrong there. -adam -adam On Mon, Feb 10, 2020 at 12:35 PM Gregory Nutt <spudan...@gmail.com> wrote: > > >> Received 50 buffers: 66.8 Kb (avg 1.3 Kb) in 101.00 Sec ( 0.6 > >>> Kb/Sec) > >>> > >> So maybe it's going very very slowly? > > > > Okay. I just didn't way long enough. Remove CONFIG_SIM_WALLTIME=y > > from your configuration and it should go a lot faster (maybe too fast). > > > > OR maybe there really is some kind of timing issue. After all, you > > did claim that the problems started with the removal of > > CONFIG_TIME_EXTENDED. > > If you enable CONFIG_SYSLOG_TIMESTAMP, then each debug output line will > be timestamped. If there are some crazy long delays in the test, that > will show you exactly where the delays are happening. > > > > -- Adam Feuer <a...@starcat.io>
