Greg, Ok, thanks. I did do that yesterday with tcpdump while trying to find the closing-early problem with the header lengths. Now with the header length calculation things look good– at low speeds, the packet exchange matches what I am getting from a Linux web server. No retransmissions, resets, or missed ACKs. I will try a high-speed capture and examine it.
I did try tcpblaster last night, and can only get about 100 KB/s maximum – about 800kbps, so much less than the 480Mbps that's possible. So that is probably part of the constraint. The SAMA5D36 has USB DMA.so it should be possible to get 100Mbps or higher... I will try with the Gigabit Ethernet and see if I can find the bottleneck. -adam On Sun, Jan 12, 2020 at 11:07 AM Gregory Nutt <spudan...@gmail.com> wrote: > > >> The first thing I would do would be to use Wireshark to see what exactly > >> the timing on the network is. > >> > > Greg, > > > > Thanks- that sounds good. Would you be willing to say more about this? > What > > exactly would you look for? > > You should see the connection, the HTTP requests and the HTTP responses, > and the socket close sequence. More importantly, you will see the times > between them and if there is anything weird going on like retransmissions. > > > -- Adam Feuer <a...@starcat.io>
