NorskSystemST2110 interface

Signature:

export interface NorskSystemST2110

Methods

Method Description

Method	Description
nic(settings)
nicAfterPreflight(settings)	Like `nic`, but resolves once the server-side gen_server is up and preflight validation has passed — without waiting for MTL_Init / MTL_Start to finish. Useful for orchestration paths that want downstream component creation (NMOS devices, senders, receivers) to overlap with NIC bring-up. The returned NIC’s `initialised` Promise still resolves when MTL is fully ready, if you want to await it separately before sending or receiving packets.
node(settings)
recommendCoresFor(settings)	Ask the server to pick a NUMA-local set of DPDK lcores for the given NIC. The server reads the NIC’s `local_cpulist` plus the kernel’s `isolcpus` / `nohz_full` sets, so callers don’t have to know the host’s CPU topology themselves — handy for tests that may run on different hardware in CI. The returned shape is exactly what `scheduling: { type: "pinned", … }` on a subsequent `nic()` call expects.

nic(settings)

nicAfterPreflight(settings)

Like nic, but resolves once the server-side gen_server is up and preflight validation has passed — without waiting for MTL_Init / MTL_Start to finish. Useful for orchestration paths that want downstream component creation (NMOS devices, senders, receivers) to overlap with NIC bring-up. The returned NIC’s initialised Promise still resolves when MTL is fully ready, if you want to await it separately before sending or receiving packets.

node(settings)

recommendCoresFor(settings)

Ask the server to pick a NUMA-local set of DPDK lcores for the given NIC. The server reads the NIC’s local_cpulist plus the kernel’s isolcpus / nohz_full sets, so callers don’t have to know the host’s CPU topology themselves — handy for tests that may run on different hardware in CI.

The returned shape is exactly what scheduling: { type: "pinned", … } on a subsequent nic() call expects.