[LU-11865] Use loopback address instead of 0 for loopback NID Created: 15/Jan/19 Updated: 16/Jan/19 Resolved: 16/Jan/19 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Sonia Sharma (Inactive) | Assignee: | Sonia Sharma (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
Currently the NID for loopback shows as "0@lo"
# lnetctl net show
net:
- net type: lo
local NI(s):
- nid: 0@lo
status: up
interfaces:
0: lo
It would be better if the loopback IP address is used instead of 0 in loopback NID.
|
| Comments |
| Comment by Andreas Dilger [ 16/Jan/19 ] |
|
What is the motivation behind this change, and why do you say "better"? Using e.g. 127.0.0.1 would IMHO add confusion because the @lo interface is not the TCP loopback interface, it is internal to LNet, so if you show 127.0.0.1 here it would give the false impression that it relates to TCP loopback, when in reality it has no relation. |
| Comment by Sonia Sharma (Inactive) [ 16/Jan/19 ] |
|
Amir, James and I were discussing this LNet sysfs patch, wherein we make providing network interface information necessary. While discussing this, we thought of having the interface name specified for loopback nid as well so as not to special case the loopback NID. In this discussion, the idea came up to have an address for "lo" NID instead of 0. I just discussed with Amir and James again on this and they agree to your thought of not confusing this with the tcp loopback. So we will keep this as it is. Thanks |