From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215475] New: RMNET data connection speed would be reduced to about 80-100Mb/s from 150Mb/s if try to re-connect it
Date: Mon, 10 Jan 2022 11:23:13 +0000 [thread overview]
Message-ID: <bug-215475-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215475
Bug ID: 215475
Summary: RMNET data connection speed would be reduced to about
80-100Mb/s from 150Mb/s if try to re-connect it
Product: Drivers
Version: 2.5
Kernel Version: 5.13.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: slark_xiao@163.com
Regression: No
Created attachment 300251
--> https://bugzilla.kernel.org/attachment.cgi?id=300251&action=edit
iperf test result
We have a Qualcomm modem device which support MBIM and RMNET over USB.
For RMNET, the download-link speed would be reduced to 80 Mb/s if re-connect
it once. The expected speed should be 150 Mb/s.
Test step as below:
1. Switch device to RMNET USB composition.
2. Connect it to host PC(kernel 5.13).
3. Start a data connection with nmcli related settings.
4. Start a iperf test with simulated network(CMW500). Test result is about
145 Mb/s ,and protocol is TCP.
5. Disconnect the connection by turning off the signal, setting AT+CFUN=0， or
deleting the data connection in the host.
6. Re-connect it again.
7. The TCP iperf test could only reach to about 80-100Mb/s.
This issue can not reproduced with MBIM port.
Also, Windows can't reproduce the RMNET issue.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-01-10 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 11:23 bugzilla-daemon [this message]
2022-01-10 11:38 ` [Bug 215475] New: RMNET data connection speed would be reduced to about 80-100Mb/s from 150Mb/s if try to re-connect it Greg KH
2022-01-10 11:38 ` [Bug 215475] " bugzilla-daemon
2022-01-12 8:03 ` bugzilla-daemon
2022-01-12 8:41 ` Greg KH
2022-01-12 8:41 ` bugzilla-daemon
2022-02-25 9:39 ` bugzilla-daemon
2022-03-02 6:25 ` bugzilla-daemon
2022-03-07 6:40 ` bugzilla-daemon
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=bug-215475-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).