From: Hiago De Franco <hiagofranco@gmail.com>
To: oneukum@suse.com
Cc: davem@davemloft.net, edumazet@google.com,
hiago.franco@toradex.com, hiagofranco@gmail.com, kuba@kernel.org,
linux-usb@vger.kernel.org, pabeni@redhat.com
Subject: Re: Question regarding CDC NCM and VNC performance issue
Date: Tue, 5 Dec 2023 09:55:41 -0300 [thread overview]
Message-ID: <20231205125542.14854-1-hiagofranco@gmail.com> (raw)
In-Reply-To: <a13fc273-20ee-4027-9508-7e8e93a9cd29@suse.com>
From: Hiago De Franco <hiago.franco@toradex.com>
Hi Oliver,
In my last reply, I sent the ping command with the wrong target. This is
the correct one:
$ ping 192.168.11.1
PING 192.168.11.1 (192.168.11.1) 56(84) bytes of data.
...
64 bytes from 192.168.11.1: icmp_seq=23 ttl=64 time=2.23 ms
64 bytes from 192.168.11.1: icmp_seq=24 ttl=64 time=2.27 ms
64 bytes from 192.168.11.1: icmp_seq=25 ttl=64 time=2.14 ms
64 bytes from 192.168.11.1: icmp_seq=26 ttl=64 time=2.24 ms
64 bytes from 192.168.11.1: icmp_seq=27 ttl=64 time=2.26 ms
64 bytes from 192.168.11.1: icmp_seq=28 ttl=64 time=2.14 ms
64 bytes from 192.168.11.1: icmp_seq=29 ttl=64 time=3106 ms
64 bytes from 192.168.11.1: icmp_seq=30 ttl=64 time=2097 ms
64 bytes from 192.168.11.1: icmp_seq=31 ttl=64 time=1073 ms
64 bytes from 192.168.11.1: icmp_seq=32 ttl=64 time=48.7 ms
64 bytes from 192.168.11.1: icmp_seq=33 ttl=64 time=2791 ms
64 bytes from 192.168.11.1: icmp_seq=34 ttl=64 time=1781 ms
64 bytes from 192.168.11.1: icmp_seq=35 ttl=64 time=757 ms
64 bytes from 192.168.11.1: icmp_seq=36 ttl=64 time=6.48 ms
64 bytes from 192.168.11.1: icmp_seq=37 ttl=64 time=5828 ms
64 bytes from 192.168.11.1: icmp_seq=38 ttl=64 time=4821 ms
64 bytes from 192.168.11.1: icmp_seq=39 ttl=64 time=3793 ms
64 bytes from 192.168.11.1: icmp_seq=40 ttl=64 time=2773 ms
64 bytes from 192.168.11.1: icmp_seq=41 ttl=64 time=1745 ms
64 bytes from 192.168.11.1: icmp_seq=42 ttl=64 time=725 ms
64 bytes from 192.168.11.1: icmp_seq=43 ttl=64 time=6.11 ms
64 bytes from 192.168.11.1: icmp_seq=44 ttl=64 time=2467 ms
64 bytes from 192.168.11.1: icmp_seq=45 ttl=64 time=1457 ms
64 bytes from 192.168.11.1: icmp_seq=46 ttl=64 time=437 ms
64 bytes from 192.168.11.1: icmp_seq=47 ttl=64 time=8.34 ms
64 bytes from 192.168.11.1: icmp_seq=48 ttl=64 time=2403 ms
64 bytes from 192.168.11.1: icmp_seq=49 ttl=64 time=1397 ms
64 bytes from 192.168.11.1: icmp_seq=50 ttl=64 time=373 ms
64 bytes from 192.168.11.1: icmp_seq=51 ttl=64 time=3212 ms
64 bytes from 192.168.11.1: icmp_seq=52 ttl=64 time=2197 ms
64 bytes from 192.168.11.1: icmp_seq=53 ttl=64 time=1169 ms
64 bytes from 192.168.11.1: icmp_seq=54 ttl=64 time=145 ms
64 bytes from 192.168.11.1: icmp_seq=55 ttl=64 time=7.27 ms
64 bytes from 192.168.11.1: icmp_seq=56 ttl=64 time=2303 ms
64 bytes from 192.168.11.1: icmp_seq=57 ttl=64 time=1301 ms
64 bytes from 192.168.11.1: icmp_seq=58 ttl=64 time=273 ms
64 bytes from 192.168.11.1: icmp_seq=59 ttl=64 time=2.01 ms
64 bytes from 192.168.11.1: icmp_seq=60 ttl=64 time=2335 ms
64 bytes from 192.168.11.1: icmp_seq=61 ttl=64 time=1333 ms
64 bytes from 192.168.11.1: icmp_seq=62 ttl=64 time=305 ms
64 bytes from 192.168.11.1: icmp_seq=63 ttl=64 time=2.14 ms
64 bytes from 192.168.11.1: icmp_seq=64 ttl=64 time=2.26 ms
64 bytes from 192.168.11.1: icmp_seq=65 ttl=64 time=2.25 ms
64 bytes from 192.168.11.1: icmp_seq=66 ttl=64 time=2.19 ms
64 bytes from 192.168.11.1: icmp_seq=67 ttl=64 time=2.20 ms
64 bytes from 192.168.11.1: icmp_seq=68 ttl=64 time=2.24 ms
64 bytes from 192.168.11.1: icmp_seq=69 ttl=64 time=2.21 ms
64 bytes from 192.168.11.1: icmp_seq=70 ttl=64 time=2.11 ms
64 bytes from 192.168.11.1: icmp_seq=71 ttl=64 time=2.19 ms
64 bytes from 192.168.11.1: icmp_seq=72 ttl=64 time=2.19 ms
^C
--- 192.168.11.1 ping statistics ---
72 packets transmitted, 72 received, 0% packet loss, time 71445ms
rtt min/avg/max/mdev = 2.011/757.798/5827.620/1266.170 ms, pipe 6
So everything is going well, around 2.1 ms, until I connect to VNC. When
this happens, the ping spikes to 1000~2000 ms. Then when I close the
connection, it gets back to ~2 ms. I can also see some "TCP
Retransmission" on Wireshark.
On 05.12.23 13:38, Oliver Neukum wrote:
> 1514 is a standard ethernet packet. What is wNtbOutMaxDatagrams on your
> device?
I couldn't find this file on my device. On my Host Linux machine it
reports 0.
Regards,
Hiago
next prev parent reply other threads:[~2023-12-05 12:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 18:37 Question regarding CDC NCM and VNC performance issue Hiago De Franco
2023-12-05 9:50 ` Oliver Neukum
2023-12-05 12:22 ` Hiago De Franco
2023-12-05 12:38 ` Oliver Neukum
2023-12-05 12:55 ` Hiago De Franco [this message]
2023-12-05 20:14 ` Hiago De Franco
2023-12-06 12:21 ` Oliver Neukum
2023-12-06 16:23 ` Hiago De Franco
2023-12-07 9:41 ` Oliver Neukum
2023-12-07 10:03 ` Francesco Dolcini
2023-12-07 11:07 ` Oliver Neukum
2023-12-07 11:38 ` Maciej Żenczykowski
2023-12-07 18:57 ` Hiago De Franco
2023-12-07 19:37 ` Maciej Żenczykowski
2023-12-11 20:28 ` Hiago De Franco
2023-12-11 20:44 ` Maciej Żenczykowski
2023-12-12 9:48 ` Oliver Neukum
2023-12-12 20:32 ` Hiago De Franco
2023-12-12 21:21 ` Oliver Neukum
2023-12-13 1:11 ` Maciej Żenczykowski
2023-12-15 21:20 ` Hiago De Franco
2023-12-15 21:44 ` Maciej Żenczykowski
2023-12-18 14:34 ` Oliver Neukum
2023-12-18 20:59 ` Hiago De Franco
2023-12-18 23:00 ` Maciej Żenczykowski
2023-12-19 8:45 ` Oliver Neukum
2023-12-19 12:19 ` Maciej Żenczykowski
2023-12-19 13:24 ` Oliver Neukum
2023-12-19 16:25 ` Maciej Żenczykowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231205125542.14854-1-hiagofranco@gmail.com \
--to=hiagofranco@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hiago.franco@toradex.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox