-
Notifications
You must be signed in to change notification settings - Fork 217
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
feature: adding blocking in a table convert function #2625
feature: adding blocking in a table convert function #2625
Conversation
/intelci: run |
/intelci: run |
/intelci: run |
/intelci: run |
/intelci: run |
/intelci: run |
/intelci: run |
std::int64_t propose_block_size(const sycl::queue& q, const std::int64_t r) { | ||
constexpr std::int64_t fsize = sizeof(Float); | ||
return 0x10000l * (8 / fsize); | ||
} |
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.
Can it be exposed to an optimization library?
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.
I think its better to do it in another pr, due to we have a lot of local propose_block_size functions, and some of them are not aligned
/intelci: run |
const byte_t* const gathered_byte = | ||
reinterpret_cast<const byte_t*>(gathered_device_unique.get()); | ||
byte_t* const dst_byte = reinterpret_cast<byte_t*>(dst_device); |
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.
why is 110 const byte_t* and 112 byte_t* const?
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.
One line is source, and other one is a consumer aka destination)
/intelci: run |
Have these been changes been tested with the original spark issue? |
it was exactly tested with the spark issue |
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.
LGTM
Description
Its feature for adding support of extremely big datasets in all algorithms