> I'm suggesting that nobody will be taking e.g core-image-sato and be able to
> work out of the box with dpdk installed, as they'll need a toolchain to build
> their own application against dpdk. Let's just not install it in the images, 
> and a
> user will either write a recipe for their image or create a SDK image to which
> they can trivially add dpdk.

Ross, 

DPDK suite comes with library and sample application that in past release run 
out-of-box
to demonstrate the feature. Romley & crystal-forest are communication grade 
platform
which is expected to have both DPDK and QAT technology demonstrated. 

The challenge is if we don't have the features & examples pre-installed on the 
sample image
that is packaged into release tarball, customer have to build them from scratch 
to try out
the DPDK examples. Yes, I do agree that it is trivial.

I do agree that customer sample app is still need to be compiled against the 
shared library.
So, they will have to rebuild some image again.

I am looping in CID TME to give in their opinion on this subject matter as he 
owns the supporting 
customer part just to check with him whether it is ok to leave the trivial 
change to end-customer who is using
yocto to do that themselves. If I remember correctly, that will require some 
documentation update
on their end too.

Thanks for the response anyway, let's do what is right and also convenient for 
the user... 
I believe that we can reach some agreement here.... 

Joel & Abhishek, 
        What is your thought of not having DPDK &QAT technology pre-installed 
on the
core-image-sato & core-image-sato-sdk images? Do you think that your customer 
will follow
some recommendation documented in manual to add them into their build recipe to 
add in 
DPDK and DPDK samples? 
        Do take note that, in the past on the NDA recipe that was released out 
in previous
product line,  DPDK & QAT are preinstalled onto the core-image-sato binary that 
is released
as test image. What is your thought there? 
-- 
_______________________________________________
meta-intel mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-intel

Reply via email to