From: Greg KH <gregkh@linuxfoundation.org>
To: Tomasz Janowski <tomasz.janowski@duke.edu>
Cc: USB list <linux-usb@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"889831@bugs.debian.org" <889831@bugs.debian.org>
Subject: Re: USB rndis_host - slow download transfers, RX errors
Date: Thu, 8 Feb 2018 17:37:25 +0100 [thread overview]
Message-ID: <20180208163725.GB9421@kroah.com> (raw)
In-Reply-To: <3383838.qbvETOe8ma@janowski>
On Thu, Feb 08, 2018 at 10:53:20AM -0500, Tomasz Janowski wrote:
> On Thursday, February 8, 2018 3:43:05 PM EST Greg KH wrote:
> > On Thu, Feb 08, 2018 at 02:16:08PM +0000, Tomasz Janowski, Ph.D. wrote:
> > > Dear USB developers,
> > >
> > > Based on my google research, the problem I experience seems to happen
> > > with some newer smartphones. My test case is Samsung Galaxy S8 (SM-950U1).
> > > I am trying to use USB tethering and everything seems to work as expected
> > > (modules are loaded, Ethernet devices are up and running, dhcp works
> > > fine). I can connect to the external world using both LTE or wireless
> > > network on the phone.
> > >
> > > Now, the problem is that the download speeds are terrible, around 64 KB/s,
> > > while uploads are fast, the order of 15 MB/s. These speeds do not depend
> > > on the wireless service provider: the results are similar when I tether
> > > wi-fi. The USB Ethernet interface on the Linux host reports a lot of
> > > receive errors (attached: device_state.txt), while kernel reports bad
> > > rndis messages (attached: kernel.log.txt).
> > >
> > > Windows 10 works great with the same hardware (same PC and same phone),
> > > with uploads and downloads in the order of 150 Mbit/s, which is probably
> > > as fast as my wireless network can do. But some people reported issues
> > > with older Windows drivers too. Is possible that some newer version of
> > > RNDIS protocol is around and Linux hasn't updated its RNDIS module yet?
> >
> > Hey, I was _just_ talking to someone at Google about this same issue
> > yesterday, you beat him sending this same type of report to the mailing
> > list, nice job :)
> >
> > Yes, this is not good, and we should work to resolve this, but first,
> > what kernel version are you using? I think some fixes for the rndis
> > driver went in recently to 4.15, but it would be good to verify that
> > this isn't already resolved.
>
> The error messages which I have attached were produced by a precompiled Debian
> kernel: "Linux version 4.14.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org)
> (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #1 SMP Debian 4.14.13-1~bpo9+1
> (2018-01-14)".
>
> But I have downloaded the most recent version of the kernel from the official
> git repository (last commit: Jan 31, 2018) and it had exactly the same
> problem. Unless a patch was submitted within the last week, the issue is still
> there.
>
> Should I get the version as of today and test it again?
If you find a 4.15 tree, that would be great to test, but odds are, the
issues are still there.
I'll try to carve out some time to look at this tomorrow, as I have a
bunch of Android devices to test with, and there's no good reason why
Windows should be slower than Linux for stuff like this. We should be
able to go as fast as the device lets us. Most likely we are doing
something "stupid" in the rndis driver somewhere :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-02-08 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <151801953766.3584.1741662034970121249.reportbug@theory.chem.duke.edu>
[not found] ` <1518039563.2617.15.camel@decadent.org.uk>
2018-02-08 14:16 ` USB rndis_host - slow download transfers, RX errors Tomasz Janowski, Ph.D.
[not found] ` <BL2PR05MB2196BF871003A1E636D714B883F30-OPySxP7SCtAm5UMXViuLsLJUF9Gbu2OwvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-02-08 14:43 ` Greg KH
[not found] ` <20180208144305.GA20594-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2018-02-08 15:53 ` Tomasz Janowski
2018-02-08 16:37 ` Greg KH [this message]
2018-02-08 17:02 ` Tomasz Janowski
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=20180208163725.GB9421@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=889831@bugs.debian.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tomasz.janowski@duke.edu \
/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).