Details
-
New Feature
-
Resolution: Fixed
-
Major
-
Lustre 2.6.0
-
None
-
5798
Description
This ticket has been created to track the main development work for the Dynamic LNet Config project.
Attachments
Issue Links
- is duplicated by
-
LU-1071 able to handle many lnet routes
- Resolved
- is related to
-
LU-5734 LNet dynamic control: lnet_dyn_add_ni() can't clean up failed NI in some cases
- Resolved
-
LU-5568 kernel crash when when network initialization failed
- Resolved
-
LU-5838 DLC: inconsistent nameing of seqno vs seq_no
- Resolved
-
LU-5849 DLC: parse networks function needs to return the number of parsed networks
- Resolved
-
LU-5854 DLC: lnetctl import failed as Failed to handle token:2 [state=0, rc=-1]
- Resolved
-
LU-5861 DLC: lnet startup script doesn't invoke lnetctl properly
- Resolved
-
LU-5874 DLC: the ongoing traffic was interrupted after adding a new network interface
- Resolved
-
LU-5875 DLC: failed adding an existing network interface when there is traffic ongoing
- Resolved
-
LU-5884 bad lnet conf causes LBUG
- Resolved
-
LUDOC-204 Update Lustre Manual for Dynamic LNET Config
- Closed
-
LU-5098 /proc/sys/lnet/routes is stupid
- Open
-
LU-5850 DLC: lnet_startup_lndnis should clean up after itself
- Resolved
- is related to
-
LU-1279 failure trying to mount two targets at the same time after boot
- Resolved