You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The programmatic configuration API already signifies failure to detect NUMA resources through return values, that the calling code is supposed to inspect. Therefore, when using the programmatic API, we shouldn't be emitting warnings like:
[0 - 7fca1b871b80] 0.000000 {5}{module_config}: Module numa can not detect resources.
when NUMA detection fails.
The text was updated successfully, but these errors were encountered:
When calling bool ModuleConfig::get_resource(const std::string name, T &value), do we care about why it returns false? Currently, there are two cases that could return a false, one is module fails to detect resources, the other is name is not a valid one. If we want to know the reason of returning false, the best option is to replace bool with RealmStatus, which is an error code.
The programmatic configuration API already signifies failure to detect NUMA resources through return values, that the calling code is supposed to inspect. Therefore, when using the programmatic API, we shouldn't be emitting warnings like:
when NUMA detection fails.
The text was updated successfully, but these errors were encountered: