On May 21, 2019, at 5:46 PM, Bairen YI <b...@connect.ust.hk> wrote:
tf.load_library or tf.load_op_library is what most add-ons do today. They tend to create ABI incompatibility problems though. The central point of making everything depending on C API only is to avoid this kind of issue.
See https://github.com/tensorflow/tensorflow/issues/27067 for details.
On May 21, 2019, at 5:42 PM, Jeroen Bédorf <jer...@minds.ai> wrote:
Good point! I was wondering the same thing but forgot to add it to my questions list :|
I was guessing there would be some Python command we had to use to load the plugin, but I did not see it mentioned anywhere.
On Tue, May 21, 2019 at 11:34 AM Bairen YI <b...@connect.ust.hk> wrote:
One thing that might worth discussing is how our users are supposed to use these plugins. The C API is not available in TF Python packages right now. Do we will get to use tf.load_library as all the add-ons do today? We could create Python package wrapper for the plugins if so.
I doubt it as the Python code in TF does not use the C API directly, unlike other language bindings. But I need to give it a shot first.
> On May 21, 2019, at 4:54 PM, Jeroen Bédorf <jer...@minds.ai> wrote:
> Hi Bairen,
> During the meeting later today I will driving so it might be hard for me to speak up on certain moments, but I'll be able to listen in for sure. I did some tests with the C API and it looks quite promising and pretty complete, at least with respect to the verbs implementation on which it is based.
> Below some notes, that might be useful during the meeting if the topic comes up.
> I did some basic tests for the API:
> - Build and ran the tests in the experimental folder, all worked
> - Included the header file into the verbs plugin, adjusted the BUILD file and compiled the whole stack. Worked
> - Questions:
> * Which parts of the C++ API can we still assume to be accessible. As right now a lot of functionality and data-structs are inherited and used inside the existing plugins. For porting it makes it easier to remove/disable all header files that will no longer be accessible such that it becomes clear what can and what can't be used and has to be recreated inside the plugins themselves.
You received this message because you are subscribed to the Google Groups "SIG Networking" group.
To unsubscribe from this group and stop receiving emails from it, send an email to networking+...@tensorflow.org.
Visit this group at https://groups.google.com/a/tensorflow.org/group/networking/.
You received this message because you are subscribed to the Google Groups "SIG Build" group.
To unsubscribe from this group and stop receiving emails from it, send an email to build+un...@tensorflow.org.
Visit this group at https://groups.google.com/a/tensorflow.org/group/build/.