[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200110094027.GL2235@nanopsycho.orion>
Date: Fri, 10 Jan 2020 10:40:27 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jacob Keller <jacob.e.keller@...el.com>
Cc: netdev@...r.kernel.org, valex@...lanox.com
Subject: Re: [PATCH v2 0/3] devlink region trigger support
Thu, Jan 09, 2020 at 08:33:07PM CET, jacob.e.keller@...el.com 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.
I don't think that the netdevsim usecase is enough to merge this in. You
need a real-driver user as well.
Of course, netdevsim implementation is good to have to, but you have to
bundle selftests along with that.
>
>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(-)
>
>--
>2.25.0.rc1
>
Powered by blists - more mailing lists