-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add log messages about kvikIO compatibility mode #13363
Add log messages about kvikIO compatibility mode #13363
Conversation
CUDF_LOG_INFO("Writing a file using kvikIO, with compatibility mode {}.", | ||
_kvikio_file.is_compat_mode_on() ? "on" : "off"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also log for the else
branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to log anything in the else branch because it calls make_cufile_output
, which includes the logging for that path (whether GDS was used or not).
Same goes for the other file, just with make_cufile_input
.
@@ -42,6 +42,8 @@ class file_source : public datasource { | |||
{ | |||
if (detail::cufile_integration::is_kvikio_enabled()) { | |||
_kvikio_file = kvikio::FileHandle(filepath); | |||
CUDF_LOG_INFO("Reading a file using kvikIO, with compatibility mode {}.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similarly.
…fea-kvikio-compat-log
…into fea-kvikio-compat-log
/merge |
Description
Log whether kvikIO's compatibility mode is on for a given file input/output.
Checklist