From: Hiago De Franco <hiagofranco@gmail.com>
To: linux-usb@vger.kernel.org
Cc: Oliver Neukum <oliver@neukum.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Hiago De Franco <hiago.franco@toradex.com>
Subject: Question regarding CDC NCM and VNC performance issue
Date: Mon, 4 Dec 2023 15:37:51 -0300 [thread overview]
Message-ID: <20231204183751.64202-1-hiagofranco@gmail.com> (raw)
From: Hiago De Franco <hiago.franco@toradex.com>
Hi,
I hope this email finds you well. I would like to ask a question
regarding the usage of CDC NCM and VCN on an ARM device running the Linux
kernel, connected to a host PC, also running Linux, via USB.
I have successfully set up a CDC NCM connection, where my device acts as
a DHCP server, and the connection is established without any issues.
Now, I have a VNC server running on the device. However, when I connect to
the VNC server, the performance is extremely slow and it also freezes,
making it unusable. Interestingly, when I simultaneously launch iperf3
using the same NCM connection, the VNC performance improves significantly.
The VNC remains smooth as long as iperf3 is active. When iperf3 finishes,
the VNC returns to its frozen or slow state.
I've tested the same setup with Windows 11, and in that case, the VNC
operates normally without any issues. I've also compared the network
traffic of both Windows and Linux connections using Wireshark but haven't
identified anything relevant.
Has anyone encountered a similar issue before? Could this be related to
the size or quantity of transmitted packages?
Any insights or assistance on this matter would be greatly appreciated.
Thanks,
Hiago
next reply other threads:[~2023-12-04 18:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 18:37 Hiago De Franco [this message]
2023-12-05 9:50 ` Question regarding CDC NCM and VNC performance issue 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
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=20231204183751.64202-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=oliver@neukum.org \
--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