linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215475] RMNET data connection speed would be reduced to about 80-100Mb/s from 150Mb/s  if try to re-connect it
Date: Mon, 07 Mar 2022 06:40:31 +0000	[thread overview]
Message-ID: <bug-215475-208809-x9DdEZx98p@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215475-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215475

--- Comment #6 from slark_xiao@163.com ---
Make a update about this issue.
  When we change rx_urb_size in the host side and keep it same as the QMAP
related QMI, this issue is "fixed".
  I also checked some old commit which related with rx_urb_size, let's say 
https://patchwork.kernel.org/project/linux-usb/patch/20200803065105.8997-1-yzc666@netease.com/
and
https://patchwork.ozlabs.org/project/netdev/patch/20200909091302.20992-1-dnlplm@gmail.com/#2524381.
They tried to update the rx_urb_size to make QMAP works better. But these
commits seems have been rejected.
  So do we have any new solutions or workarounds about changing the
rx_urb_size?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2022-03-07  6: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
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 [this message]

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-x9DdEZx98p@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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).