From: "Bjørn Mork" <bjorn@mork.no>
To: Daniele Palmas <dnlplm@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
yzc666@netease.com, David Miller <davem@davemloft.net>,
kuba@kernel.org, netdev@vger.kernel.org,
linux-usb <linux-usb@vger.kernel.org>,
carl <carl.yin@quectel.com>
Subject: Re: [PATCH] qmi_wwan: support modify usbnet's rx_urb_size
Date: Mon, 03 Aug 2020 12:40:54 +0200 [thread overview]
Message-ID: <87lfiw9fm1.fsf@miraculix.mork.no> (raw)
In-Reply-To: <CAGRyCJER3J4BkLohcPumdKUkQ9g39YsjERac5CSrY2-8jj+N7A@mail.gmail.com> (Daniele Palmas's message of "Mon, 3 Aug 2020 12:33:03 +0200")
Daniele Palmas <dnlplm@gmail.com> writes:
> Il giorno lun 3 ago 2020 alle ore 11:49 Greg KH
> <gregkh@linuxfoundation.org> ha scritto:
>>
>> Where does QMI_WDA_SET_DATA_FORMAT come from?
>>
>
> This is a request of Qualcomm proprietary protocol used, among other
> things, to configure data aggregation for modems. There's an open
> source userspace implementation in the libqmi project
> (https://cgit.freedesktop.org/libqmi/tree/data/qmi-service-wda.json)
>
>> And the commit log says that this "depends on the chipset being used",
>> so why don't you know that at probe time, does the chipset change? :)
>>
>
> Me too does not understand this, I let the author explain...
>
>> > Currently there's a workaround for setting rx_urb_size i.e. changing
>> > the network interface MTU: this is fine for most uses with qmap, but
>> > there's the limitation that certain values (multiple of the endpoint
>> > size) are not allowed.
>>
>> Why not just set it really high to start with? That should not affect
>> any older devices, as the urb size does not matter. The only thing is
>> if it is too small that things can not move as fast as they might be
>> able to.
>>
>
> Yes, this was proposed in the past by Bjørn
> (https://lists.freedesktop.org/archives/libqmi-devel/2020-February/003221.html),
> but I was not sure about issues with old modems.
Ah, right. Forgot about that.
> Now I understand that there are no such issues, then I agree this is
> the simplest solution: I've seen modems requiring as much as 49152,
> but usually the default for qmap is <= 16384.
>
> And, by the way, increasing the rx urb size is required also in
> non-qmap mode, since the current value leads to babbling issues with
> some chipsets (mine
> https://www.spinics.net/lists/linux-usb/msg198025.html and Paul's
> https://lists.freedesktop.org/archives/libqmi-devel/2020-February/003217.html),
> so I think we should definitely increase this also for non-qmap mode.
>
> Bjørn, what do you think?
I think we have good enough reasons to increase the rx urb size by
default. Let's try.
Bjørn
next prev parent reply other threads:[~2020-08-03 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 6:51 [PATCH] qmi_wwan: support modify usbnet's rx_urb_size yzc666
2020-08-03 8:16 ` Greg KH
2020-08-03 8:26 ` Daniele Palmas
2020-08-03 9:49 ` Greg KH
2020-08-03 10:33 ` Daniele Palmas
2020-08-03 10:40 ` Bjørn Mork [this message]
2020-08-03 10:35 ` 答复: " Carl Yin(殷张成)
2020-08-03 10:32 ` Bjørn Mork
2020-08-03 12:08 ` 答复: " Carl Yin(殷张成)
2020-08-03 14:05 ` Bjørn Mork
2020-08-03 8:38 ` Sergei Shtylyov
2020-08-03 10:01 ` kernel test robot
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=87lfiw9fm1.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=carl.yin@quectel.com \
--cc=davem@davemloft.net \
--cc=dnlplm@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yzc666@netease.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;
as well as URLs for NNTP newsgroup(s).