Linux USB
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Hiago De Franco <hiagofranco@gmail.com>, oneukum@suse.com
Cc: davem@davemloft.net, edumazet@google.com,
	hiago.franco@toradex.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 13:38:06 +0100	[thread overview]
Message-ID: <a13fc273-20ee-4027-9508-7e8e93a9cd29@suse.com> (raw)
In-Reply-To: <20231205122204.10556-1-hiagofranco@gmail.com>



On 05.12.23 13:22, Hiago De Franco wrote:

Hi,

> During the ping, nothing changes, VNC continues to be extremely slow.

I was wondering whether you ping itself has bad delays.

> I switched from NCM to ECM for testing purposes. On ECM, everything works
> seamlessly without any issues. It appears that the problem may be specific
> to the combination of NCM and the Linux host machine, as the setup works
> fine on Windows.
> 
> I'm curious if there are issues with NCM and small USB packet lengths.
> The VNC application tends to send numerous small packets (1514 bytes).

1514 is a standard ethernet packet. What is wNtbOutMaxDatagrams on your
device?

	Regards
		Oliver

  reply	other threads:[~2023-12-05 12:38 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 [this message]
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=a13fc273-20ee-4027-9508-7e8e93a9cd29@suse.com \
    --to=oneukum@suse.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hiago.franco@toradex.com \
    --cc=hiagofranco@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-usb@vger.kernel.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