[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3397d02d-5329-b63e-99b1-30a001929391@intel.com>
Date: Thu, 9 Jan 2020 12:13:22 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: netdev@...r.kernel.org
Cc: valex@...lanox.com, jiri@...nulli.us
Subject: Re: [PATCH v2 0/3] devlink region trigger support
On 1/9/2020 11:33 AM, Jacob Keller wrote:
> This series consists of patches to enable devlink to request a snapshot via
> a new DEVLINK_CMD_REGION_TRIGGER_SNAPSHOT.
>
> A reviewer might notice that the devlink health API already has such support
> for handling a similar case. However, the health API does not make sense in
> cases where the data is not related to an error condition.
>
> In this case, using the health API only for the dumping feels incorrect.
> Regions make sense when the addressable content is not captured
> automatically on error conditions, but only upon request by the devlink API.
>
> The netdevsim driver is modified to support the new trigger_snapshot
> callback as an example of how this can be used.
>
As mentioned by Jakub on an earlier comment, I wanted to clarify: I
implemented this in the netdevsim driver because I wanted to test that
the changes actually worked as expected.
I'm planning on making use of this in an Intel driver soon, but do not
yet have patches ready to send to the list.
Thanks,
Jake
> Jacob Keller (3):
> devlink: add callback to trigger region snapshots
> devlink: introduce command to trigger region snapshot
> netdevsim: support triggering snapshot through devlink
>
> drivers/net/ethernet/mellanox/mlx4/crdump.c | 4 +-
> drivers/net/netdevsim/dev.c | 37 ++++++++++++-----
> include/net/devlink.h | 12 ++++--
> include/uapi/linux/devlink.h | 2 +
> net/core/devlink.c | 45 +++++++++++++++++++--
> 5 files changed, 80 insertions(+), 20 deletions(-)
>
Powered by blists - more mailing lists