[LU-5850] DLC: lnet_startup_lndnis should clean up after itself Created: 03/Nov/14  Updated: 20/Feb/15  Resolved: 09/Jan/15

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.7.0

Type: Improvement Priority: Minor
Reporter: Amir Shehata (Inactive) Assignee: Amir Shehata (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-5734 LNet dynamic control: lnet_dyn_add_ni... Resolved
is related to LU-2456 Dynamic LNet Config Main Development ... Resolved
Rank (Obsolete): 16381

 Description   

The design intent of LNet APIs is that they clean up after themselves if they fail, to avoid having the caller invoke clean up methods.

Need to ensure that lnet_startup_lndnis does the same. Currently it's up to the caller to to cleanup if lnet_startup_lndnis() fails.

With the DLC changes, the logic of the code was modified to handle loading networks dynamically. Part of that change stops lnet_startup_lndnis() from shutting down Nets that were brought up before a failure occurred. The reason for that is we didn't want to clean up all networks that have been brought up already if a network which is being dynamically brought up fails.

However, according to Isaac the underlying design intent of LNet APIs is that they do proper cleanup in case of failure, so that callers don't have to perform this clean up, thus repeating the clean up code multiple times in the callers.

This design intent needs to be restored.



 Comments   
Comment by James A Simmons [ 07/Jan/15 ]

Now that LU-5374 has landed is this resolved?

Generated at Sat Feb 10 01:55:04 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.