From: Greg KH <greg@kroah.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [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 12:38:29 +0100 [thread overview]
Message-ID: <YdwatYUKUG7broo4@kroah.com> (raw)
In-Reply-To: <bug-215475-208809@https.bugzilla.kernel.org/>
On Mon, Jan 10, 2022 at 11:23:13AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> 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
Does this also happen on 5.16?
> 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.
If you look at the usb traces, is the data the same? Any long pauses?
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-10 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 11:23 [Bug 215475] New: RMNET data connection speed would be reduced to about 80-100Mb/s from 150Mb/s if try to re-connect it bugzilla-daemon
2022-01-10 11:38 ` Greg KH [this message]
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=YdwatYUKUG7broo4@kroah.com \
--to=greg@kroah.com \
--cc=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).