From: subashab@codeaurora.org
To: Aleksander Morgado <aleksander@aleksander.es>
Cc: "Bjørn Mork" <bjorn@mork.no>, "Daniele Palmas" <dnlplm@gmail.com>,
"Network Development" <netdev@vger.kernel.org>,
stranche@codeaurora.org
Subject: Re: RMNET QMAP data aggregation with size greater than 16384
Date: Thu, 05 Aug 2021 16:57:00 -0600 [thread overview]
Message-ID: <77b850933d9af8ddbc21f5908ca0764d@codeaurora.org> (raw)
In-Reply-To: <CAAP7ucK7EeBPJHt9XFp7bd5cGXtH5w2VGgh3yD7OA9SYd5JkJw@mail.gmail.com>
> I may be mistaken then in how this should be setup when using rmnet.
> For the qmi_wwan case using add_mux/del_mux (Daniele correct me if
> wrong!), we do need to configure the MTU of the master interface to be
> equal to the aggregation data size reported via QMI WDA before
> creating any mux link; see
> http://paldan.altervista.org/linux-qmap-qmi_wwan-multiple-pdn-setup/
>
> I ended up doing the same here for the rmnet case; but if it's not
> needed I can definitely change that. I do recall that I originally had
> left the master MTU untouched in the rmnet case and users had issues,
> and increasing it to the aggregation size solved that; I assume that's
> because the MTU should have been increased to accommodate the extra
> MAP header as you said. How much more size does it need on top of the
> 1500 bytes?
You need to use an additional 4 bytes for MAPv1 and 8 bytes for
MAPv4/v5.
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2021-08-05 22:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 22:45 RMNET QMAP data aggregation with size greater than 16384 Aleksander Morgado
2021-08-05 19:10 ` subashab
2021-08-05 20:32 ` Aleksander Morgado
[not found] ` <CAGRyCJHYkH4_FvTzk7BFwjMN=iOTN_Y2=4ueY=s3rJMQO9j7uw@mail.gmail.com>
2021-08-05 21:01 ` Aleksander Morgado
2021-08-05 21:12 ` Daniele Palmas
2021-08-05 22:57 ` subashab [this message]
2021-08-06 14:08 ` Aleksander Morgado
2021-08-06 18:42 ` subashab
2021-08-06 19:58 ` Bjørn Mork
2021-08-06 20:22 ` Aleksander Morgado
2021-08-06 22:30 ` subashab
2021-08-07 10:55 ` Bjørn Mork
2021-08-09 21:40 ` subashab
2021-08-12 12:02 ` Daniele Palmas
2021-08-13 6:21 ` subashab
2021-08-13 6:25 ` Bjørn Mork
2021-09-03 13:55 ` Daniele Palmas
2021-09-08 6:21 ` subashab
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=77b850933d9af8ddbc21f5908ca0764d@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=aleksander@aleksander.es \
--cc=bjorn@mork.no \
--cc=dnlplm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stranche@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.