On 24. 9. 2024 15:57, Jeremy Spewock wrote:
On Tue, Sep 24, 2024 at 5:12 AM Juraj Linkeš wrote:
I have some thoughts for the future:
1a. The traffic generator is specified per-node, so maybe we could also
change the binding to be for the whole lifetime of the TG node,
1b. But the same is tr
On Tue, Sep 24, 2024 at 5:12 AM Juraj Linkeš wrote:
>
> I have some thoughts for the future:
> 1a. The traffic generator is specified per-node, so maybe we could also
> change the binding to be for the whole lifetime of the TG node,
> 1b. But the same is true for the SUT node as well, right? After
I have some thoughts for the future:
1a. The traffic generator is specified per-node, so maybe we could also
change the binding to be for the whole lifetime of the TG node,
1b. But the same is true for the SUT node as well, right? After we do
the port update (with kernel driver), we can just bin
From: Jeremy Spewock
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
4 matches
Mail list logo
