-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
3
-
9223372036854775807
Right now, if the LNet is not configured, a NID won't be bound to its own NUMA node, which will lead to suboptimal throughput during testing.
Asking every customer to configure LNet on the client is a big usability issue, LNet should be able to bind the NIDs to their own NUMA node by default, probably it should even override the config.
This setting is so obvious to me that I'm not sure if I'm missing some contexts.