From: Stephen Hemminger <stephen@networkplumber.org>
To: Roman Khromenok <roma55592@yandex.ru>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH 0/3] net/intel: make link state configurable on device start
Date: Sun, 4 Oct 2026 09:13:33 -0700 [thread overview]
Message-ID: <20261004091333.6585bf1b@phoenix.local> (raw)
In-Reply-To: <cover.1790970122.git.roma55592@yandex.ru>
On Fri, 2 Oct 2026 21:43:35 +0200
Roman Khromenok <roma55592@yandex.ru> 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.
prev parent reply other threads:[~2026-10-04 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 19:43 [PATCH 0/3] net/intel: make link state configurable on device start Roman Khromenok
2026-10-02 19:43 ` [PATCH 1/3] net/ice: " Roman Khromenok
2026-10-02 19:43 ` [PATCH 2/3] net/i40e: " Roman Khromenok
2026-10-02 19:43 ` [PATCH 3/3] net/ixgbe: " Roman Khromenok
2026-10-03 16:18 ` [PATCH 0/3] net/intel: " Stephen Hemminger
2026-10-03 21:53 ` Roman Khromenok
2026-10-04 16:15 ` Stephen Hemminger
2026-10-04 16:13 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261004091333.6585bf1b@phoenix.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=roma55592@yandex.ru \
--cc=vladimir.medvedkin@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.