From: David Miller <davem@davemloft.net>
To: talgi@mellanox.com
Cc: netdev@vger.kernel.org, tariqt@mellanox.com, saeedm@mellanox.com,
f.fainelli@gmail.com, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH net] net/dim: Update DIM start sample after each DIM iteration
Date: Thu, 22 Nov 2018 11:37:42 -0800 (PST) [thread overview]
Message-ID: <20181122.113742.1342070809724360835.davem@davemloft.net> (raw)
In-Reply-To: <1542810503-51548-1-git-send-email-talgi@mellanox.com>
From: Tal Gilboa <talgi@mellanox.com>
Date: Wed, 21 Nov 2018 16:28:23 +0200
> On every iteration of net_dim, the algorithm may choose to
> check for the system state by comparing current data sample
> with previous data sample. After each of these comparison,
> regardless of the action taken, the sample used as baseline
> is needed to be updated.
>
> This patch fixes a bug that causes DIM to take wrong decisions,
> due to never updating the baseline sample for comparison between
> iterations. This way, DIM always compares current sample with
> zeros.
>
> Although this is a functional fix, it also improves and stabilizes
> performance as the algorithm works properly now.
>
> Performance:
> Tested single UDP TX stream with pktgen:
> samples/pktgen/pktgen_sample03_burst_single_flow.sh -i p4p2 -d 1.1.1.1
> -m 24:8a:07:88:26:8b -f 3 -b 128
>
> ConnectX-5 100GbE packet rate improved from 15-19Mpps to 19-20Mpps.
> Also, toggling between profiles is less frequent with the fix.
>
> Fixes: 8115b750dbcb ("net/dim: use struct net_dim_sample as arg to net_dim")
> Signed-off-by: Tal Gilboa <talgi@mellanox.com>
> Reviewed-by: Tariq Toukan <tariqt@mellanox.com>
Applied and queued up for -stable.
prev parent reply other threads:[~2018-11-23 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 14:28 [PATCH net] net/dim: Update DIM start sample after each DIM iteration Tal Gilboa
2018-11-22 19:37 ` David Miller [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=20181122.113742.1342070809724360835.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew.gospodarek@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=talgi@mellanox.com \
--cc=tariqt@mellanox.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).