[LU-12256] Use D_NETTRACE for LND code, and D_NET for LNet code Created: 30/Apr/19 Updated: 05/May/19 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Chris Horn | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
It would be useful to be able to toggle the LND and LNet debug output independently. Sometimes the LND output is not interesting when looking at issues in the LNet layer. This is especially true as complex new features are being added at the the LNet layer (Multi-Rail, Dynamic Discovery, LNet Health, etc.). Currently, only kgnilnd utilizes the D_NETTRACE mask, so I suggest we switch all LNDs to use this mask for their debug output. |
| Comments |
| Comment by Chris Horn [ 05/May/19 ] |
|
Ideally I think we'd have three masks available. D_NET for general LNet layer messages, D_LND, for general LND layer messages, and D_NETTRACE which would be equivalent to the D_TRACE but employed only at the LNet and LND layer to show function entry/exit. |