Missing Documentation for Integration Wrappers

[David_K_5]

On Chao Y's webpage for the IPP Integration Wrappers, section 2.1 says:

"Getting Started instructions are provided in the Integration Wrappers Developer Guide and Reference.  You can find this document the following folder available after you install the Intel® IPP Integration Wrappers Preview package: /interfaces/integration_wrappers."

However, this does not appear to be the case, at least for the Linux or Mac packages.  The Developer Guide and Reference is actually missing from these packages.

[Zhen_Z_Intel]

Hi David,

Sorry for that, seems the package is lack of document folder, we will update the package and the article. Thanks for posting this problem. 

Best regards,
Fiona

[David_K_5]

Still waiting for it ....

[Zhen_Z_Intel]

Hi David,

Sorry for let you waiting... I just received message that approved to put new document on website. We have many processes & legal validation for packaging and publishing. I will upload in next week. Hope it won't affect your work progress.

Best regards,
Fiona

[Zhen_Z_Intel]

Hi David,

I've already uploaded the guide of Integration Wrapper for IPP, please refer it. Thanks.

Best regards,
Fiona

[David_K_5]

Hi Fiona,

Just in time.  Thank you!

David

[Zhen_Z_Intel]

Hi David,

We are very glad to get using feedback from our customer. How's your feeling with Integration Wrapper of IPP? Do you have any feedback or feature request? If you do, please do not hesitate to post your problem on Premier support or this forum, thanks.

Best regards,
Fiona

[David_K_5]

Is the openmp mode stable with iw/iw++?  From the announcement webpage, there are some code snippets showing use with openmp.  Yet, the provided html documentation does not make any reference to its use with openmp (only tbb).

We have Mac systems and we use openmp.  When we make the default libipp_iw library (by specifying CONF=release instead of CONF=release_tbb), we only get a serial library.  Of course, we were able to find and modify the default builds to use the OpenMP interface, but we are concerned that it is not fully tested yet and perhaps should not be used at this time.

Can you provide the rest of the working example from the website page, so that we can see the recommended usage with openmp?

Also, is there a reason why shared libraries are not built by default (for some of the ipp libs as well)?

Lastly, if we adopt iw/iw++, would there be any restrictions for commercial deployment of our apps?  Specifically, how should our apps be re-distributed?

Thank you.

[Pavel_V_Intel]

Hello David,

"CONF=release_tbb" build options relates only to examples and doesn't provide any TBB threading inside IW.

By default IW itself doesn't utilize threading of any kind. It is designed to be threaded externally, as snippets in doc and webpage shows (how to use IW tiling interface with external OpenMP "for" cycle). This usage is stable, tested and should work without problems. However I should warn you that since IW has "preview" status, its API may be changed in the next release.

Additionally there is IW_ENABLE_THREADING_LAYER define in the iw_core.h which can be set to 1 to use IPP Threading Layer libraries which are threaded with OpenMP. It should work fine, but its functionality is limited to resize and bilateral filter for now.

Can you provide the rest of the working example from the website page, so that we can see the recommended usage with openmp?

These examples are fully self-contained so there is nothing else to show, they also can be found in the doc under "Tiling and Threading" section. iw_resize example also uses threading with both TBB and OpenMP. However OpenMP is disabled for Mac due to Apple clang limitations. It can work with proper compiler specified as CC and Makefiles modifications to remove OS X checks.

Also, is there a reason why shared libraries are not built by default (for some of the ipp libs as well)?

Static libraries are in priority due to less problems/restrictions with development and usage. IW was never built as shared library yet and has no proper entry points in the source. We may add shared build support in the future.

Lastly, if we adopt iw/iw++, would there be any restrictions for commercial deployment of our apps?  Specifically, how should our apps be re-distributed?

I believe conditions are the same as with general IPP library. But I am not a specialist in the matter.

[Chao_Y_Intel]

Hi

For this question:
>>if we adopt iw/iw++, would there be any restrictions for commercial deployment of our apps?  Specifically, how should our apps be re-distributed?
The libraries are the same with other Intel IPP libraries. Here is the FAQ for the license and redistribution:
https://software.intel.com/en-us/articles/intel-integrated-performance-primitives-faq

It is permitted to redistribute your application, and no royalty fee for redistribution of your application.

Thanks,
Chao