- This topic has 0 replies, 1 voice, and was last updated 3 weeks, 4 days ago by
.
-
Posts
-
Dear FPGA experts,
On behalf of FABRIC team, I wanted to inform you about the upcoming changes towards making any FPGA to be used by any experiment on FABRIC and seek your inputs.
Just a little background: A couple of different workflows (ESNet/NEU/OCT) exist right now. Every FPGA on FABRIC is pinned to a specific workflow. The primary reason is that changing from one workflow to another involves a reboot of VM and cold reboot of the host machine. This involves experimenters waiting till the changes are made to the host machine. On FABRIC end, we have had to drive out other active experimenters so that host machine can be cold-rebooted. The time involved varies from a few hours to a few weeks. This is not productive both for experimenters and FABRIC admins.
Why not provide the necessary hooks in the hands of experts? That is where we are heading towards. We are planning a new API that will run a series of commands including rescan on the host machine. This should avoid rebooting of host machine that disrupts other experimenters.
Ask: As FPGA experts, we seek your support in adopting the changes and sharing any comments or concerns.
Please let us know your thoughts and comments.
regs
Ganesh
- You must be logged in to reply to this topic.