OP primitive cache: use memory as signature for MKLDNN storage type #11
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.
Description
For Convolution/FC OPs, we can use NDArray dims/shape to do primitive cache signature, for some other OPs, we need to consider memory layout also, to unify the interface, we would like all OPs to pass NDArray type to AddSign and AddSign function will convert NDArray to memory type and do signature. With this change, convolution/FC OPs will also use memory to do signature, from testing, we almost didn't see any increase for convolution primitive cache count (using NDArray vs using memory to do sign) so it probably should be ok to use memory to sign convolution also.
Checklist
Essentials
make lint
)