On Fri, 2 Oct 2026 21:43:35 +0200 Roman Khromenok <[email protected]> wrote:
> Starting a port always brings its link up, so the link partner sees > the port as soon as the application starts it. An application that > enables ports only after its own configuration is applied, such as > a firewall or a switch, cannot keep a disabled port dark: it can only > bring the link down right after rte_eth_dev_start(), and the link > partner may still see the link flap. The point of start is to signal that the application is ready to send and receive packets. I would expect the normal startup sequence is: 1. EAL init 2. Detect devices 3. Configure internal state 4. Configure devices. 5. Start devices A device should be dark from 2 to 5. No packets coming in or out and link is down.
