On 12. 8. 2024 19:22, jspew...@iol.unh.edu wrote:
From: Jeremy Spewock <jspew...@iol.unh.edu> The DTS framework in its current state supports binding ports to different drivers on the SUT node but not the TG node. The TG node already has the information that it needs about the different drivers that it has available in the configuration file, but it did not previously have access to the devbind script, so it did not use that information for anything. This patch moves the steps to copy the DPDK tarball into the node class rather than the SUT node class, and calls this function on the TG node as well as the SUT. It also moves the driver binding step into the Node class and triggers the same pattern of binding to ports that existed on the SUT on the TG.
This is a very inefficient way to do this. We'll have to build DPDK twice and that's very time consuming. I was thinking in terms of just copying the script to the TG node and storing its location on the TG node. We should have access to the script whether DTS is run from the repository or a tarball.
