-
Notifications
You must be signed in to change notification settings - Fork 916
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
[WIP] SHA-1 and SHA-2 hashes #6020
Closed
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -644,6 +644,12 @@ std::unique_ptr<column> hash(table_view const& input, | |
switch (hash_function) { | ||
case (hash_id::HASH_MURMUR3): return murmur_hash3_32(input, initial_hash, mr, stream); | ||
case (hash_id::HASH_MD5): return md5_hash(input, mr, stream); | ||
case (hash_id::HASH_SHA1): return sha1(input, mr, stream); | ||
case (hash_id::HASH_SHA224): return sha256_base(input, true, mr, stream); | ||
case (hash_id::HASH_SHA256): return sha256_base(input, false, mr, stream); | ||
case (hash_id::HASH_SHA384): return sha512_base(input, true, mr, stream); | ||
case (hash_id::HASH_SHA512): return sha512_base(input, false, mr, stream); | ||
|
||
default: return nullptr; | ||
} | ||
} | ||
|
@@ -765,6 +771,23 @@ std::unique_ptr<column> murmur_hash3_32(table_view const& input, | |
return output; | ||
} | ||
|
||
std::unique_ptr<column> sha1(table_view const& input, | ||
rmm::mr::device_memory_resource* mr, | ||
cudaStream_t stream) { | ||
} | ||
|
||
std::unique_ptr<column> sha256_base(table_view const& input, | ||
bool truncate_output, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Don't use a bool parameter. Use an enum class with a descriptive name so it's more obvious at the callsite what this controls. |
||
rmm::mr::device_memory_resource* mr, | ||
cudaStream_t stream) { | ||
} | ||
|
||
std::unique_ptr<column> sha512_base(table_view const& input, | ||
bool truncate_output, | ||
rmm::mr::device_memory_resource* mr, | ||
cudaStream_t stream) { | ||
} | ||
|
||
} // namespace detail | ||
|
||
std::unique_ptr<column> hash(table_view const& input, | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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'm concerned about using up all of the available constant memory with all of these lookup tables. There's only 64KB available.
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.
Also, what will the access pattern be across threads in the same warp? If it is random, rather than uniform, I think just
__device__ const
would be better.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.
Happy to change the approach, was asked to use
__device__ __constant__
in the md5 hashing. Should I swap back to thethread_safe_per_context_cache
?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.
Oops, Mark's reply didn't show up in my initial comment.
Access pattern for each thread is sequential, but there's nothing synchronizing each thread across the warp -- so I think the access within a warp would effectively be random.