Skip to content
Snippets Groups Projects
Commit aebbd7df authored by Jakub Kicinski's avatar Jakub Kicinski Committed by David S. Miller
Browse files

docs: devlink: clarify the scope of snapshot id


In past discussions Jiri explained snapshot ids are cross-region.
Explain this in the docs.

v3: new patch

Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
Reviewed-by: default avatarJiri Pirko <jiri@mellanox.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 043b3e22
No related branches found
No related tags found
No related merge requests found
...@@ -14,6 +14,10 @@ Region snapshots are collected by the driver, and can be accessed via read ...@@ -14,6 +14,10 @@ Region snapshots are collected by the driver, and can be accessed via read
or dump commands. This allows future analysis on the created snapshots. or dump commands. This allows future analysis on the created snapshots.
Regions may optionally support triggering snapshots on demand. Regions may optionally support triggering snapshots on demand.
Snapshot identifiers are scoped to the devlink instance, not a region.
All snapshots with the same snapshot id within a devlink instance
correspond to the same event.
The major benefit to creating a region is to provide access to internal The major benefit to creating a region is to provide access to internal
address regions that are otherwise inaccessible to the user. address regions that are otherwise inaccessible to the user.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please to comment