-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[CPU] Use Dnnl executor to avoid extra dnnl primitve desc query #16372
[CPU] Use Dnnl executor to avoid extra dnnl primitve desc query #16372
Conversation
@usstq , FIY |
const dnnl::engine& engine) { | ||
execPrim = dnnl::convolution_forward(pd); | ||
|
||
const dnnl::engine& engine) : DnnlExecutor(pd) { | ||
if (inMemDesc != pd.src_desc()) { |
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 change it to getSrcDesc()
since pd.src_desc()
is slow?
also pd.weights_desc()
and pd.dst_desc()
in following lines
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.
Good point. Changed accordingly. Thank you!
@dmitry-gorokhov , could you please review? |
Details:
Since v3.1 it was observed that early inefficient dnnl::primitive_desc query became even slower. It was decided to store input, output and scratchpad memory descriptors in the DnnlExecutor to avoid dnnl::primitive_desc query calls at runtime.
Tickets: