From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: davem@davemloft.net, Nogah Frankel <nogahf@mellanox.com>,
netdev@vger.kernel.org, oss-drivers@netronome.com,
xiyou.wangcong@gmail.com, edumazet@google.com,
Yuval Mintz <yuvalm@mellanox.com>
Subject: Re: [PATCH net-next v2] net: sched: red: don't reset the backlog on every stat dump
Date: Wed, 17 Jan 2018 11:50:43 +0100 [thread overview]
Message-ID: <20180117105043.GB2114@nanopsycho> (raw)
In-Reply-To: <20180115040126.14190-1-jakub.kicinski@netronome.com>
Mon, Jan 15, 2018 at 05:01:26AM CET, jakub.kicinski@netronome.com wrote:
>Commit 0dfb33a0d7e2 ("sch_red: report backlog information") copied
>child's backlog into RED's backlog. Back then RED did not maintain
>its own backlog counts. This has changed after commit 2ccccf5fb43f
>("net_sched: update hierarchical backlog too") and commit d7f4f332f082
>("sch_red: update backlog as well"). Copying is no longer necessary.
>
>Tested:
>
>$ tc -s qdisc show dev veth0
>qdisc red 1: root refcnt 2 limit 400000b min 30000b max 30000b ecn
> Sent 20942 bytes 221 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 1260b 14p requeues 14
> marked 0 early 0 pdrop 0 other 0
>qdisc tbf 2: parent 1: rate 1Kbit burst 15000b lat 3585.0s
> Sent 20942 bytes 221 pkt (dropped 0, overlimits 138 requeues 0)
> backlog 1260b 14p requeues 14
>
>Recently RED offload was added. We need to make sure drivers don't
>depend on resetting the stats. This means backlog should be treated
>like any other statistic:
>
> total_stat = new_hw_stat - prev_hw_stat;
>
>Adjust mlxsw.
>
>Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Acked-by: Jiri Pirko <jiri@mellanox.com>
next prev parent reply other threads:[~2018-01-17 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 4:01 [PATCH net-next v2] net: sched: red: don't reset the backlog on every stat dump Jakub Kicinski
2018-01-16 19:05 ` David Miller
2018-01-17 7:33 ` Nogah Frankel
2018-01-17 10:50 ` Jiri Pirko [this message]
2018-01-17 19:29 ` David Miller
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=20180117105043.GB2114@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=nogahf@mellanox.com \
--cc=oss-drivers@netronome.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yuvalm@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