forked from facebookincubator/velox
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add status return and fixes for nulls (facebookincubator#10954)
Summary: - Add per instruction status return block above the BlockStatus array. Copy the Blockstatus array to host and do not use unified memory for this. The instruction return has a grid-scope status where all grid scope statuses are directly after the the BlockStatuses. Additionally there can be a block level status with n bytes per TB. These are after all the grid level statuses. - Zero out the grid level statuses in reader, so that subsequent ops are guaranteed a zero grid level status. Block level statuses are uninitialized. If an instruction is continuable, it will first set its grid status and optionally its block level statuses. - Add one status copy at the end of each pipeline. This serves for all error and continuability information. - test coverage for cases with nulls with different numbers of rows per tb, including a case of TB doing more rows than the stripe has, in which case griddize can be skipped. - Add an optional counter for tracking host to device transfer latency separately from compute latency. Pull Request resolved: facebookincubator#10954 Reviewed By: Yuhta Differential Revision: D62397804 Pulled By: oerling fbshipit-source-id: 3ede44b15289838d183c979c50168c931f03266b
- Loading branch information
1 parent
baaf559
commit 741876f
Showing
24 changed files
with
507 additions
and
146 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.