-
Notifications
You must be signed in to change notification settings - Fork 6.8k
support slice on MKLDNN arrays better #12303
Comments
Yes, I think it's doable and worth to do. In other words, we need an MKL-DNN based slice OP. Do you need our engineer to help with this kind of functionality? |
@pengzhao-intel if your team has bandwidth to make it happen, it'll be great. |
OK, we will take over this work and submit PR later. |
@mxnet-label-bot : [MKLDNN, Feature Request] |
@safrooze Could you provide a use case for @pengzhao-intel for testing? |
@safrooze we're starting the implementation of slide OP. |
The use case is implementing effectively a circular buffer using
And here are the interesting profiling results.
|
Thanks @safrooze :) |
@safrooze Thanks for your usecase. I have implemented the first edition of an MKL-DNN supported version for slice OP. slice w/o MKL-DNN
slice w/ MKL-DNN
|
Great results @fall4knight! Does it make sense to you that |
@safrooze I think the reason is that in your usecase you set |
@fall4knight Any update on submitting a PR for this fix? |
Thanks @safrooze We are still WIP for the different type of slice, like sliceChannel, and the backward path. |
@pengzhao-intel , @safrooze slice w/o MKL-DNN
slice w/ MKL-DNN
|
Closed via #13730 . |
Currently, slice on an MKLDNN array requires to convert the array to the default layout before taking a slice. However, the MKLDNN library actually provides a view for MKLDNN memory. As such, by taking advantage of the MKLDNN view, we don't really need to convert data layout for slice.
For details, please see the discussion here: oneapi-src/oneDNN#306, oneapi-src/oneDNN#69, oneapi-src/oneDNN#290
@pengzhao-intel @TaoLv @azai91 @safrooze
The text was updated successfully, but these errors were encountered: