From: Daniele Palmas <dnlplm@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Eric Dumazet" <edumazet@google.com>,
"Subash Abhinov Kasiviswanathan" <quic_subashab@quicinc.com>,
"Sean Tranchetti" <quic_stranche@quicinc.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Alexander Lobakin" <alexandr.lobakin@intel.com>,
"Gal Pressman" <gal@nvidia.com>, "Bjørn Mork" <bjorn@mork.no>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] add tx packets aggregation to ethtool and rmnet
Date: Thu, 1 Dec 2022 11:48:32 +0100 [thread overview]
Message-ID: <CAGRyCJGAMGxW04_XQjrUforZ6G7Y4gcR=CvkzZDiP0vqHnB-pg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw58hiRprhvCiek+YSOSb_y2QsQVWQMzrPARgGJGj9gEew@mail.gmail.com>
Hello Dave,
Il giorno mer 30 nov 2022 alle ore 16:04 Dave Taht
<dave.taht@gmail.com> ha scritto:
>
> On Wed, Nov 30, 2022 at 5:15 AM Daniele Palmas <dnlplm@gmail.com> wrote:
> >
> > Hello maintainers and all,
> >
> > this patchset implements tx qmap packets aggregation in rmnet and generic
> > ethtool support for that.
> >
> > Some low-cat Thread-x based modems are not capable of properly reaching the maximum
> > allowed throughput both in tx and rx during a bidirectional test if tx packets
> > aggregation is not enabled.
> >
> > I verified this problem with rmnet + qmi_wwan by using a MDM9207 Cat. 4 based modem
> > (50Mbps/150Mbps max throughput). What is actually happening is pictured at
> > https://drive.google.com/file/d/1gSbozrtd9h0X63i6vdkNpN68d-9sg8f9/view
>
> Thank you for documenting which device this is. Is it still handing in
> 150ms of bufferbloat in good conditions,
> and 25 seconds or so in bad?
>
New Flent test results available at
https://drive.google.com/drive/folders/1-rpeuM2Dg9rVdYCP0M84K4Ook5kcZTWc?usp=share_link
From what I can understand, it seems to me a bit better, but not
completely sure how much is directly related to the changes of v2.
Regards,
Daniele
next prev parent reply other threads:[~2022-12-01 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 12:46 [PATCH net-next v2 0/3] add tx packets aggregation to ethtool and rmnet Daniele Palmas
2022-11-30 12:46 ` [PATCH net-next v2 1/3] ethtool: add tx aggregation parameters Daniele Palmas
2022-12-02 0:21 ` Jakub Kicinski
2022-12-02 11:42 ` Daniele Palmas
2022-11-30 12:46 ` [PATCH net-next v2 2/3] net: qualcomm: rmnet: add tx packets aggregation Daniele Palmas
2022-11-30 16:35 ` kernel test robot
2022-12-01 2:01 ` kernel test robot
2022-11-30 12:46 ` [PATCH net-next v2 3/3] net: qualcomm: rmnet: add ethtool support for configuring tx aggregation Daniele Palmas
2022-11-30 15:04 ` [PATCH net-next v2 0/3] add tx packets aggregation to ethtool and rmnet Dave Taht
2022-12-01 10:48 ` Daniele Palmas [this message]
2022-12-01 15:22 ` Dave Taht
2022-12-02 16:56 ` Daniele Palmas
2022-12-02 17:27 ` Dave Taht
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='CAGRyCJGAMGxW04_XQjrUforZ6G7Y4gcR=CvkzZDiP0vqHnB-pg@mail.gmail.com' \
--to=dnlplm@gmail.com \
--cc=alexandr.lobakin@intel.com \
--cc=bjorn@mork.no \
--cc=corbet@lwn.net \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_stranche@quicinc.com \
--cc=quic_subashab@quicinc.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).