From: Moshe Shemesh <moshe@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>, Jakub Kicinski <kuba@kernel.org>,
Jiri Pirko <jiri@nvidia.com>,
netdev@vger.kernel.org
Cc: Moshe Shemesh <moshe@mellanox.com>
Subject: [PATCH iproute2-net v2 0/3] devlink: Add devlink reload action limit and stats
Date: Mon, 7 Dec 2020 07:35:19 +0200 [thread overview]
Message-ID: <1607319322-20970-1-git-send-email-moshe@mellanox.com> (raw)
Introduce new options on devlink reload API to enable the user to select
the reload action required and constrains limits on these actions that he
may want to ensure.
Add reload stats to show the history per reload action per limit.
Patch 1 adds the new API reload action and reload limit options to
devlink reload command.
Patch 2 adds pr_out_dev() helper function and modify monitor function to
use it.
Patch 3 adds reload stats and remote reload stats to devlink dev show.
Moshe Shemesh (3):
devlink: Add devlink reload action and limit options
devlink: Add pr_out_dev() helper function
devlink: Add reload stats to dev show
devlink/devlink.c | 268 +++++++++++++++++++++++++++++++++++++++--
man/man8/devlink-dev.8 | 34 ++++++
2 files changed, 291 insertions(+), 11 deletions(-)
--
2.26.2
next reply other threads:[~2020-12-07 5:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 5:35 Moshe Shemesh [this message]
2020-12-07 5:35 ` [PATCH iproute2-net v2 1/3] devlink: Add devlink reload action and limit options Moshe Shemesh
2020-12-09 2:46 ` David Ahern
2020-12-09 5:32 ` Moshe Shemesh
2020-12-07 5:35 ` [PATCH iproute2-net v2 2/3] devlink: Add pr_out_dev() helper function Moshe Shemesh
2020-12-07 5:35 ` [PATCH iproute2-net v2 3/3] devlink: Add reload stats to dev show Moshe Shemesh
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=1607319322-20970-1-git-send-email-moshe@mellanox.com \
--to=moshe@mellanox.com \
--cc=dsahern@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.