This page outlines the LNet features that are either being implemented or being considered for implementation.
| Name | Assigned Release | Jira Ticket | Scope & Requirements Document | High-level Design Document |
|---|---|---|---|---|
| LNet Resiliency | Lustre 2.12 | LNet Resiliency Requirements | Presentation on timeouts from 2014 by Alexey Lyashkov | |
| LNet Router alignment | Lustre 2.13 | Multi-Rail Routing Requirements | Multi-Rail Routing Requirements Patch Description | |
| LNet UDSP (Router selection) | Lustre 2.13 | UDSP Requirements | UDSP HLD | |
| LNet Unit Test Framework (LUTF) - Move up | Lustre 2.13+ | LUTF Requirements | LUTF HLD | |
| IPv6 Support | Lustre 2.14+ | |||
| Dynamic NIDs | Lustre 2.14+ | |||
| LNet Statistics improvement | Lustre 2.14+ | LNet Sysfs Requirements | LNet Sysfs HLD | |
| Ptlrpc and LNet threading model | There is a discrepancy between LNet and ptlrpc threading and how CPT affinity works. There should be a single threading model for both LNet and ptlrpc. | |||
| New Fast Memory registration | ||||
| CQ Polling API | ||||
| Draining QP | ||||
| lnet_selftest improvement | ||||
| SWIM Protocol for Network Discovery | ||||
| Correlating job stats with LNet stats | ||||
| Lustre traffic QoS | ||||
| LNet beyond Lustre | Preliminary Requirements | |||
| LNet Control Messages | A proposed feature by Alexey Lyashkov. LNet should have something like an ICMP, to have the ability to report some bad situations to sender like:
|