[GitHub] ashokei commented on issue #10092: No "full" pooling convention support with MKL-DNN

2018-03-13 Thread GitBox
ashokei commented on issue #10092: No "full" pooling convention support with 
MKL-DNN
URL: 
https://github.com/apache/incubator-mxnet/issues/10092#issuecomment-372879308
 
 
   not been implemented by mkldnn for this specific case, hence with fix in 
#10021 we fallback to CPU just like any other feature/configure that is not 
currently implemented/supported-by-mkldnn-integration.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] ashokei commented on issue #10092: No "full" pooling convention support with MKL-DNN

2018-03-13 Thread GitBox
ashokei commented on issue #10092: No "full" pooling convention support with 
MKL-DNN
URL: 
https://github.com/apache/incubator-mxnet/issues/10092#issuecomment-372866683
 
 
   @marcoabreu The issue is with a specific SSD-VGG16-reduced model, in which 
pooling convention of full (only with maxpool) causes failure. 
   
   The solution in #10021 is to fall-back to CPU maxpool/full-pooling 
convention.  This fallback approach is used anytime we have a config/option not 
supported by mkl-dnn integration yet. So this is not a "bug" per se. It would 
be feature that may be enabled / implemented in future. I would remove "bug" as 
it is misleading for this ticket. With the fix in #10021 this issue will be 
resolved.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] ashokei commented on issue #10092: No "full" pooling convention support with MKL-DNN

2018-03-13 Thread GitBox
ashokei commented on issue #10092: No "full" pooling convention support with 
MKL-DNN
URL: 
https://github.com/apache/incubator-mxnet/issues/10092#issuecomment-372866683
 
 
   @marcoabreu The issue is with a specific SSD-VGG16-reduced model, in which 
pooling convention of full (only with maxpool) causes failure. 
   
   The solution in #10021 is to fall-back to CPU maxpool/full-pooling 
convention.  This fallback approach is used anytime we have a config/option not 
supported by mkl-dnn integration yet. So this is not a "bug" per se. It would 
be a feature that may be enabled / implemented in future. 
   
   I would remove "bug" as it is misleading for this ticket. With the fix in 
#10021 this issue will be resolved.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] ashokei commented on issue #10092: No "full" pooling convention support with MKL-DNN

2018-03-13 Thread GitBox
ashokei commented on issue #10092: No "full" pooling convention support with 
MKL-DNN
URL: 
https://github.com/apache/incubator-mxnet/issues/10092#issuecomment-372866683
 
 
   @marcoabreu The issue is with a specific SSD-VGG16-reduced model, in which 
pooling convention of full (only with maxpool) causes failure. 
   
   The solution in #10021 is to fall-back to CPU maxpool/full-pooling 
convention.  This fallback approach is used anytime we have a config/option not 
supported by mkl-dnn integration yet. So this is not a "bug" per se. It would 
be feature that may be enabled / implemented in future. I would remove "bug" as 
it is misleading for this ticket. With the fix in @10021 this issue will be 
resolved.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services