All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, jiri@mellanox.com, mlxsw@mellanox.com,
	dsahern@gmail.com, roopa@cumulusnetworks.com,
	nikolay@cumulusnetworks.com, andy@greyhouse.net,
	pablo@netfilter.org, jakub.kicinski@netronome.com,
	pieter.jansenvanvuuren@netronome.com, andrew@lunn.ch,
	f.fainelli@gmail.com, Ido Schimmel <idosch@mellanox.com>
Subject: [RFC PATCH iproute2-next 0/5] Add devlink-trap support
Date: Tue, 28 May 2019 15:26:13 +0300	[thread overview]
Message-ID: <20190528122618.30769-1-idosch@idosch.org> (raw)
In-Reply-To: <20190528122136.30476-1-idosch@idosch.org>

From: Ido Schimmel <idosch@mellanox.com>

This patchset adds devlink-trap support in iproute2.

Patch #1 is just for convenience, so that people do not need to pull the
kernel headers themselves. Will be dropped for non-RFC version.

Patch #2 increases the number of options devlink can handle.

Patches #3-#5 gradually add support for all devlink-trap commands.

See individual commit messages for example usage and output.

Ido Schimmel (5):
  Update kernel headers
  devlink: Increase number of supported options
  devlink: Add devlink trap set and show commands
  devlink: Add devlink trap group set and show commands
  devlink: Add devlink trap monitor support

 devlink/devlink.c            | 543 +++++++++++++++++++++++++++++++++--
 include/uapi/linux/devlink.h |  68 +++++
 2 files changed, 594 insertions(+), 17 deletions(-)

-- 
2.20.1


  parent reply	other threads:[~2019-05-28 12:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 12:21 [RFC PATCH net-next 00/12] Add drop monitor for offloaded data paths Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 01/12] devlink: Create helper to fill port type information Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 02/12] devlink: Add packet trap infrastructure Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 03/12] devlink: Add generic packet traps and groups Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 04/12] Documentation: Add devlink-trap documentation Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 05/12] netdevsim: Add devlink-trap support Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 06/12] Documentation: Add description of netdevsim traps Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 07/12] mlxsw: pci: Query and store PCIe bandwidth during init Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 08/12] mlxsw: core: Add API to set trap action Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 09/12] mlxsw: reg: Add new " Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 10/12] mlxsw: Add layer 2 discard trap IDs Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 11/12] mlxsw: Add trap group for layer 2 discards Ido Schimmel
2019-05-28 12:21 ` [RFC PATCH net-next 12/12] mlxsw: spectrum: Add devlink-trap support Ido Schimmel
2019-05-28 12:26 ` Ido Schimmel [this message]
2019-05-28 12:26   ` [RFC PATCH iproute2-next 1/5] Update kernel headers Ido Schimmel
2019-05-28 12:26   ` [RFC PATCH iproute2-next 2/5] devlink: Increase number of supported options Ido Schimmel
2019-05-28 12:26   ` [RFC PATCH iproute2-next 3/5] devlink: Add devlink trap set and show commands Ido Schimmel
2019-05-28 12:26   ` [RFC PATCH iproute2-next 4/5] devlink: Add devlink trap group " Ido Schimmel
2019-05-28 12:26   ` [RFC PATCH iproute2-next 5/5] devlink: Add devlink trap monitor support Ido Schimmel
2019-05-29  1:32 ` [RFC PATCH net-next 00/12] Add drop monitor for offloaded data paths Florian Fainelli

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=20190528122618.30769-1-idosch@idosch.org \
    --to=idosch@idosch.org \
    --cc=andrew@lunn.ch \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@mellanox.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jiri@mellanox.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=pablo@netfilter.org \
    --cc=pieter.jansenvanvuuren@netronome.com \
    --cc=roopa@cumulusnetworks.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 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.