opensm SA DB dump/restore: SA DB persistence
Status from this message: Applied. Thanks.
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest2 patches 2 repliesApplied
- v23 patches 12 repliesSuperseded
- v13 patches 0 repliesSuperseded
Patches in v3 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | opensm SA DB dump/restore: load SA DB only onceopensm/ | +17 | 1 reply | |
| 2/2 | opensm SA DB dump/restore: added option to dump SA DB on every sweepopensm/ opensm/ opensm/ | +17 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH 0/2 v3] opensm SA DB dump/restore: SA DB persistence
Hi Sasha,
OSM can dump SA DB, but it is done every heavy sweep, and only when running with high verbosity, which cannot be used in production.
OSM can also load SA DB from file, but then it also stays in this static SA configuration.
The following patch series improves SA DB persistence:
1/2: Added option to load SA DB only on the first master
heavy sweep. After that SA goes to the usual (dynamic) mode of operation.
- Changes since v2: No 'sa_db_load_once' option, changed behavior of 'no_clients_rereg' option (details in the patch)
2/2: Added option to dump SA DB on every sweep (both light
and heavy), regardless of the verbosity level.
- Changes since v2: none, just rebased
-- Yevgeny
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html